Cloudflare 1.1.1.1 public DNS different as path info for 1.0.0.1 and 1.1.1.1 london

David Hubbard dhubbard at dino.hostasaurus.com
Tue Apr 3 19:20:37 UTC 2018


I'm finding it unreachable from at least one Level 3 router.  I'm seeing behavior which makes me suspect 1.1.1.1/32 has been incorrectly defined an interface IP on that device; one of our locations gets an immediate ping response for 1.1.1.1, and a traceroute of one hop, which is that first upstream hop.  1.0.0.1 is reachable like normal across several hops.

´╗┐On 4/3/18, 1:36 PM, "NANOG on behalf of George Skorup" <nanog-bounces at nanog.org on behalf of george.skorup at cbcast.com> wrote:

    1.1.1.1 not usable via Windstream peering in Chicago.
    
    # traceroute 1.1.1.1
    traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
    ...
      3  be4.agr01.chcg02-il.us.windstream.net (40.136.99.22)  5.158 ms 
    5.116 ms  7.565 ms
      4  ae13-0.cr01.chcg01-il.us.windstream.net (40.136.99.44)  4.673 ms  
    4.644 ms  4.600 ms
      5  et8-0-0-0.cr02.dlls01-tx.us.windstream.net (40.128.10.135) 27.136 
    ms  27.099 ms  27.053 ms
      6  xe0-2-3-0.cr02.dnvt01-co.us.windstream.net (40.136.97.125) 29.075 
    ms  28.381 ms  28.336 ms
      7  xe3-3-1-0.pe03.dums01-tx.us.windstream.net (173.189.57.195) 46.121 
    ms  46.193 ms  46.148 ms
      8  * * *
      9  * * *
    10  * * *
    11  * * *
    12  * * *
    13  *^C
    
    # ping 1.1.1.1
    PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
    64 bytes from 1.1.1.1: icmp_seq=1 ttl=248 time=43.2 ms
    64 bytes from 1.1.1.1: icmp_seq=2 ttl=248 time=43.9 ms
    64 bytes from 1.1.1.1: icmp_seq=3 ttl=248 time=42.8 ms
    ^C
    --- 1.1.1.1 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2002ms
    rtt min/avg/max/mdev = 42.892/43.344/43.915/0.489 ms
    
    # nslookup
     > server 1.1.1.1
    Default server: 1.1.1.1
    Address: 1.1.1.1#53
     > google.com
    ;; connection timed out; trying next origin
    ;; connection timed out; no servers could be reached
    



More information about the NANOG mailing list