Cant reach 1.1.1.1 but 1.0.0.1 works great

[sigmmaaa]

1.1.1.1 dns doesn’t work while 1.0.0.1 works

[sandro]

Have problems with 1.1.1.1? *Read Me First*

Here are some tips for troubleshooting if you are having issues using Cloudflare’s Resolver. Please take a moment to review them along with the information that will help us to understand and help diagnose any issues. There are two sections to this guide. The first is for troubleshooting name resolution errors/issues and the second is for unreachability or routing issues. New Diagnostic Tool We have a new diagnostic tool which can help gather some of the information requested below. If you copy…

[sigmmaaa]

connection info

i set up everything in iv6 and iv4 correctly, also i live in Saskatchewan canada so why am i connecting to YVR. also im just using 1.1.1.1 and 1.0.0.1 for house use, not running a website or anything, i heard the benefits and it is faster than my default one from my internet provider Sasktel

[sandro]

@cs-cf

Troubleshooting Unreachability or Routing Issues

1. Please search the forum for your country name and ISP to see if the issue may have already been reported. If it has please review that post and add any comments you may have to it rather than creating a new post.
2. Please provide a traceroute for both 1.1.1.1 and 1.0.0.1 (even if you can reach one and not the other).

UNIX (Linux/macOS)
—
traceroute 1.1.1.1
traceroute 1.0.0.1

Windows
—
tracert 1.1.1.1
tracert 1.0.0.1

3. If you believe Cloudflare’s route is suboptimal, please provide a traceroute to a DNS server which you believe has better routing (we can’t always improve routing, but it’s helpful to have information/context when we communicate with ISPs and network providers).
4. If the traceroute reaches Cloudflare please also include the output for

UNIX (Linux/macOS)
—
dig +short CHAOS TXT id.server @1.1.1.1
dig +short CHAOS TXT id.server @1.0.0.1

Bonus points if you include these 2:
dig +tcp @1.1.1.1 id.server CH TXT
dig +tcp @1.0.0.1 id.server CH TXT

Windows
—
nslookup -class=chaos -type=txt id.server 1.1.1.1
nslookup -class=chaos -type=txt id.server 1.0.0.1

Bonus points if you include these 2:
nslookup -vc -class=chaos -type=txt id.server 1.1.1.1
nslookup -vc -class=chaos -type=txt id.server 1.0.0.1

5. For DNS over TLS issues:

UNIX (Linux/macOS)
—
openssl s_client -connect 1.1.1.1:853
openssl s_client -connect 1.0.0.1:853

Gold star if you also include:
kdig +tls @1.1.1.1 id.server CH TXT
kdig +tls @1.0.0.1 id.server CH TXT

Windows
—
As Windows does not have openssl installed and it does not have an alternative to kdig this step requires UNIX

6. For DNS over HTTPS (DoH) connectivity issues please also run the command below and paste the results of the file in your report as well:

UNIX (Linux/macOS)
—
curl -v ‘https://1.1.1.1/dns-query?ct=application/dns-json&name=Cloudflare.com ’

Windows
—
As Windows does not have an alternative to curl this step requires UNIX

7. If your traceroute dies at the first hop, your issue is almost certainly hardware related, your router may have a hardcoded route for 1.1.1.1. If that is the case, please provide the make/model of your router as well as your ISP.
8. Please also consider opening a ticket with your ISP for unreachability or routing related problems as well. We try very hard to work with other network providers when a problem is discovered, but sometimes those providers have other priorities. Your feedback to them helps them to determine this is an issue worth investigating.

---