1.1.1.1 unreachable, 1.0.0.1 works

Hello,

I’m having problems with reaching DNS 1.1.1.1. It seems like there’s a correct route to it but it can’t connect to DNS nor the website under https:// 1.1.1.1/. Interestingly using 1.0.0.1 as DNS works and also https://1.0.0.1/ works fine.

Debug information:

C:\>tracert 1.1.1.1
  1    <1 ms    <1 ms    <1 ms  10.0.0.1
  2    15 ms    10 ms     8 ms  ipbcc2abfe.dynamic.kabel-deutschland.de [188.194.171.254]
  3    11 ms     8 ms    10 ms  ip5886dca6.static.kabel-deutschland.de [88.134.220.166]
  4    15 ms    16 ms    15 ms  83-169-156-166.static.superkabel.de [83.169.156.166]
  5    16 ms    17 ms    17 ms  one.one.one.one [1.1.1.1]

C:\>tracert 1.0.0.1
  1     1 ms    <1 ms    <1 ms  10.0.0.1
  2    59 ms    35 ms     8 ms  ipbcc2abfe.dynamic.kabel-deutschland.de [188.194.171.254]
  3    11 ms    10 ms    10 ms  ip5886dca6.static.kabel-deutschland.de [88.134.220.166]
  4    18 ms    15 ms    20 ms  83-169-156-166.static.superkabel.de [83.169.156.166]
  5    17 ms    15 ms    16 ms  145.254.3.102
  6    19 ms    14 ms    16 ms  145.254.2.201
  7    20 ms    16 ms    14 ms  de-cix-munich.as13335.net [80.81.202.9]
  8    21 ms    15 ms    18 ms  one.one.one.one [1.0.0.1]

C:\>nslookup -class=chaos -type=txt id.server 1.1.1.1
DNS request timed out.
    timeout was 2 seconds.

C:\>nslookup -class=chaos -type=txt id.server 1.0.0.1
Server:  one.one.one.one
Address:  1.0.0.1

Nicht autorisierende Antwort:
id.server       text =

        "MUC"

C:\>nslookup -vc -class=chaos -type=txt id.server 1.1.1.1
Server:  UnKnown
Address:  1.1.1.1

*** id.server wurde von UnKnown nicht gefunden: Unspecified error.

C:\>nslookup -vc -class=chaos -type=txt id.server 1.0.0.1
Server:  one.one.one.one
Address:  1.0.0.1

Nicht autorisierende Antwort:
id.server       text =

        "MUC"

Best regards
Markus

I have the same issue. 1.1.1.1 redirects me to my residential gateway, but 1.0.0.1 doesn’t.

:wave: @amirehmarwan,

Your residential gateway is configured to use the 1.1.1.1 address itself. You can ask the manufacturer/ vendor to confirm and if they have an update to fix their hardware. It is unfortunately common that 1.1.1.1 was commonly used by folks who didn’t own it in their applications.

— OG

1 Like