Please include test result URL when you create a post in the community forum. Paste the results from → 1.1.1.1 — One of the Internet’s Fastest, Privacy-First DNS Resolver
What is the error message?
connection timed out; no servers could be reached
What is the issue you’re encountering
I am unable to use 1.1.1.1 on port 53 or access https://1.1.1.1
What steps have you taken to resolve the issue?
Connected directly to my modem to confirm it’s not my internal routing equipment.
nslookup cloudflare.com 1.1.1.1
;; connection timed out; no servers could be reached
dig cloudflare.com @1.1.1.1
;; global options: +cmd
;; connection timed out; no servers could be reached
traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 40 byte packets
1 10.0.0.1 (10.0.0.1) 3.965 ms 3.240 ms 3.399 ms
2 * * *
3 10.2.1.9 (10.2.1.9) 20.923 ms 12.165 ms 16.722 ms
4 host-24-112-x-x.vyvebroadband.net (24.112.x.x) 17.415 ms
host-24-112-x-x.vyvebroadband.net (24.112.x.x) 15.171 ms 17.734 ms
5 172.29.104.2 (172.29.104.2) 18.567 ms 19.253 ms 16.515 ms
6 172.29.0.13 (172.29.0.13) 22.810 ms
172.29.104.2 (172.29.104.2) 15.805 ms 14.987 ms
7 172.29.100.10 (172.29.100.10) 23.605 ms
172.29.0.13 (172.29.0.13) 28.979 ms
172.29.100.10 (172.29.100.10) 23.085 ms
8 one.one.one.one (1.1.1.1) 25.276 ms
172.29.100.10 (172.29.100.10) 24.929 ms
one.one.one.one (1.1.1.1) 24.438 ms
nslookup cloudflare.com 1.0.0.1
Server: 1.0.0.1
Address: 1.0.0.1#53
Non-authoritative answer:
Name: cloudflare.com
Address: 104.16.132.229
Name: cloudflare.com
Address: 104.16.133.229
dig cloudflare.com @1.0.0.1
; <<>> DiG 9.10.6 <<>> cloudflare.com @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39098
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;cloudflare.com. IN A
;; ANSWER SECTION:
cloudflare.com. 60 IN A 104.16.133.229
cloudflare.com. 60 IN A 104.16.132.229
;; Query time: 39 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Fri Mar 21 10:50:32 EDT 2025
;; MSG SIZE rcvd: 75
traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 64 hops max, 40 byte packets
1 10.0.0.1 (10.0.0.1) 3.851 ms 3.044 ms 2.873 ms
2 * * *
3 10.2.1.13 (10.2.1.13) 17.218 ms 16.861 ms 18.188 ms
4 host-24-112-x-x.vyvebroadband.net (24.112.x.x) 16.458 ms 20.723 ms
host-24-112-x-x.vyvebroadband.net (24.112.x.x) 8.277 ms
5 172.29.104.2 (172.29.104.2) 22.706 ms
172.29.104.26 (172.29.104.26) 39.425 ms
172.29.104.2 (172.29.104.2) 15.076 ms
6 * * *
7 38.142.x.x (38.142.x.x) 49.768 ms
be4746.ccr41.atl04.atlas.cogentco.com (38.122.46.217) 59.859 ms *
8 108.162.235.65 (108.162.235.65) 43.433 ms 48.050 ms
108.162.235.59 (108.162.235.59) 40.852 ms
9 one.one.one.one (1.0.0.1) 39.959 ms 146.895 ms 45.802 ms
This started occurring yesterday at around 6:30PM eastern.
Hop 8 in the traceroute to 1.1.1.1 seems to be hitting private IP range so it seems like something is going on there to cause that issue. I’m not seeing it exit from my public IP there either like 1.0.0.1.
Just wanting to confirm this is illustrating that the issue is related to my ISP. Is it possibly CGNAT? Or just a routing issue somewhere else down the line?
Thanks!