Unable to use 1.1.1.1 but 1.0.0.1 works

#1

I am not able to use 1.1.1.1 for DNS resolution but the 1.0.0.1 address is reachable.

|-[13:10:45]-> traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max
  1   10.255.255.0  28.391ms  31.054ms  30.699ms 
  2   104.12.36.1  39.079ms  31.109ms  40.789ms 
  3   99.174.25.234  394.108ms  400.495ms  498.046ms 
  4   12.122.163.158  43.272ms  47.885ms  39.996ms 
  5   12.122.2.41  42.224ms  45.680ms  39.595ms 
  6   12.122.117.121  35.862ms  35.610ms  39.855ms 
  7   192.205.36.158  37.790ms  35.895ms  34.585ms 
  8   129.250.5.59  41.590ms  38.270ms  39.263ms 
  9   129.250.4.222  38.203ms  40.159ms  39.641ms 
 10   131.103.117.38  38.017ms  37.955ms  39.387ms 
 11   *  *  * 
 12   *  *  * 
 13   *  *  * 
^C

|-[13:11:18]-> traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 64 hops max
  1   10.255.255.0  34.956ms  29.989ms  31.594ms 
  2   104.12.36.1  29.101ms  30.333ms  42.011ms 
  3   99.174.25.234  34.213ms  128.801ms  28.700ms 
  4   12.122.163.158  46.718ms  40.172ms  39.373ms 
  5   12.122.2.41  44.744ms  39.825ms  40.084ms 
  6   12.122.117.121  40.905ms  34.637ms  40.479ms 
  7   192.205.36.158  40.679ms  35.357ms  47.034ms 
  8   129.250.5.59  43.652ms  41.374ms  40.765ms 
  9   129.250.4.222  39.741ms  35.662ms  38.327ms 
 10   131.103.117.38  35.504ms  37.716ms  39.877ms 
 11   1.0.0.1  37.773ms  34.945ms  36.250ms

Is this something that I can fix on my end and if so any pointers to how?

#2

Interesting, it seems it stops right at the hop before Cloudflare. Which datacentre are you hitting?

#3

Can you advise how I can determine what datacentre I am using?

#4

Which operating system are you using?

#5

I have tried on Linux Mint 18.3 KDE and unRAID (Slackware) with the same results.

#6

In that case, whats the output of

dig +short CHAOS TXT id.server @1.0.0.1
#7 
|-[14:15:24]-> dig +short CHAOS TXT id.server @1.0.0.1
"ATL"
#8

You seem to go via Atlanta. Maybe a glitch over there.

@cloonan @cscharff

#9

I am South of Nashville, TN so Atlanta certainly would be plausible.

#10

Any ideas on how to resolve this issue? Still no joy as of this morning.

|-[09:33:34]-> traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  192.168.20.1 (192.168.20.1)  0.208 ms  0.230 ms  0.203 ms
 2  104-12-36-1.lightspeed.nsvltn.sbcglobal.net (104.12.36.1)  3.323 ms  3.494 ms  3.791 ms
 3  99.174.25.234 (99.174.25.234)  3.934 ms  4.167 ms  3.589 ms
 4  12.122.163.158 (12.122.163.158)  12.344 ms  12.170 ms  12.444 ms
 5  attga22crs.ip.att.net (12.122.2.41)  16.381 ms  13.506 ms  12.560 ms
 6  attga402igs.ip.att.net (12.122.117.121)  14.184 ms  9.210 ms  9.051 ms
 7  192.205.36.158 (192.205.36.158)  8.644 ms  8.057 ms  9.047 ms
 8  ae-1.r04.atlnga05.us.bb.gin.ntt.net (129.250.5.59)  10.834 ms  11.383 ms  12.091 ms
 9  ae-1.a00.atlnga05.us.bb.gin.ntt.net (129.250.5.92)  10.403 ms ae-0.a00.atlnga05.us.bb.gin.ntt.net (129.250.4.222)  11.696 ms ae-1.a00.atlnga05.us.bb.gin.ntt.net (129.250.5.92)  10.141 ms
10  ae-0.cloudflare.atlnga05.us.bb.gin.ntt.net (131.103.117.38)  12.248 ms  12.526 ms  10.966 ms
11  * * *
12  * * *
#11

@cloonan, @cscharff, any known issues in the ATL DC?