Having connectivity issues today to DNS

For whatever reason today I’m suddenly unable to connect to 1.1.1.1 or 1.0.0.1. Switching my backup name resolver to Google 8.8.8.8 seems to have corrected my issue.

Anyone else having issues?


dig www.disney.com 640 @1.1.1.1

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> www.disney.com 640 @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32795
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.disney.com. IN A

;; ANSWER SECTION:
www.disney.com. 299 IN CNAME video.disney.com.edgesuite.net.
video.disney.com.edgesuite.net. 14097 IN CNAME a1996.dscf1.akamai.net.
a1996.dscf1.akamai.net. 19 IN A 23.14.84.192
a1996.dscf1.akamai.net. 19 IN A 23.14.84.184

;; Query time: 65 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Aug 22 08:40:39 EDT 2019
;; MSG SIZE rcvd: 152

;; connection timed out; no servers could be reached


dig www.disney.com 640 @1.0.0.1

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> www.disney.com 640 @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 781
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.disney.com. IN A

;; ANSWER SECTION:
www.disney.com. 137 IN CNAME video.disney.com.edgesuite.net.
video.disney.com.edgesuite.net. 21114 IN CNAME a1996.dscf1.akamai.net.
a1996.dscf1.akamai.net. 19 IN A 23.14.84.192
a1996.dscf1.akamai.net. 19 IN A 23.14.84.184

;; Query time: 45 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Aug 22 08:43:28 EDT 2019
;; MSG SIZE rcvd: 152

;; connection timed out; no servers could be reached


; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> www.disney.com 640 @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24606
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.disney.com. IN A

;; ANSWER SECTION:
www.disney.com. 275 IN CNAME video.disney.com.edgesuite.net.
video.disney.com.edgesuite.net. 21252 IN CNAME a1996.dscf1.akamai.net.
a1996.dscf1.akamai.net. 19 IN A 23.14.84.184
a1996.dscf1.akamai.net. 19 IN A 23.14.84.192

;; Query time: 59 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Aug 22 08:41:10 EDT 2019
;; MSG SIZE rcvd: 152

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10967
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;640. IN A

;; AUTHORITY SECTION:
. 86375 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019082200 1800 900 604800 86400

;; Query time: 23 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Aug 22 08:41:10 EDT 2019
;; MSG SIZE rcvd: 107


dig +short CHAOS TXT id.server @1.1.1.1
;; connection timed out; no servers could be reached

dig +short CHAOS TXT id.server @1.0.0.1
;; connection timed out; no servers could be reached


traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
1 MainGateway (192.168.1.1) 2.365 ms 0.491 ms 0.362 ms
2 216.230.40.2.host.smartcitytelecom.com (216.230.40.2) 5.296 ms 5.880 ms 5.866 ms
3 mn-d01-01-vlan558.smartcitytelecom.com (66.90.8.137) 5.468 ms 5.763 ms 5.745 ms
4 one.one.one.one (1.1.1.1) 7.401 ms 7.912 ms 7.900 ms

traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 30 hops max, 60 byte packets
1 MainGateway (192.168.1.1) 0.554 ms 0.550 ms 0.613 ms
2 216.230.40.2.host.smartcitytelecom.com (216.230.40.2) 6.398 ms 6.296 ms 6.276 ms
3 mn-d01-01-vlan558.smartcitytelecom.com (66.90.8.137) 61.543 ms 61.570 ms 61.437 ms
4 mn-c03-01-gig0-1.smartcitytelecom.com (66.90.3.30) 5.533 ms 6.111 ms 5.934 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Well, you seem to be unable to connect in the first place.

Whats the output of these commands?

traceroute 1.1.1.1
traceroute 1.0.0.1

Sorry, just added that. When I use 8.8.8.8 I have no issues.

But 1.1.1.1 or 1.0.0.1 from my UBNT Gateway results in no DNS Service.

It would seem your ISP is hijacking both addresses. You’d need to contact your ISP in this regard.

I checked with them since I posted this morning and they are telling me they are not blocking anything and that 1.1.1.1 is in fact not available. They’ve tried from their end as well and are unable to get a response.

1.0.0.1 has come back online this morning and it’s now working apparently as I’m able to run a dig against it and get a response.

After thinking about it some more, though I will admit I don’t know completely how Cloudflare’s setup is working, the fact that I can get a ping back MAY just mean that I’m able to reach the edge responder on the CDN and there is in fact still no ‘service’ behind it responding on port 53.

Considering 1.0.0.1 is now working, can you run another traceroute for both addresses and post it here?

$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
1 MainGateway (192.168.1.1) 0.635 ms 0.594 ms 0.630 ms
2 216.230.40.2.host.smartcitytelecom.com (216.230.40.2) 6.258 ms 6.627 ms 6.595 ms
3 mn-d01-01-vlan558.smartcitytelecom.com (66.90.8.137) 5.856 ms 6.472 ms 6.473 ms
4 one.one.one.one (1.1.1.1) 6.403 ms 8.667 ms 8.017 ms

[email protected]nipi:~ $ traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 30 hops max, 60 byte packets
1 MainGateway (192.168.1.1) 0.584 ms 0.451 ms 0.522 ms
2 216.230.40.2.host.smartcitytelecom.com (216.230.40.2) 10.047 ms 10.477 ms 10.878 ms
3 mn-d01-01-vlan558.smartcitytelecom.com (66.90.8.137) 5.793 ms 6.630 ms 6.603 ms
4 mn-a08-01-ten2-1.smartcitytelecom.com (66.90.9.122) 6.568 ms 6.531 ms 6.880 ms
5 xe-9-0-2.bar2.Tampa1.Level3.net (4.35.213.249) 13.471 ms 15.335 ms 14.657 ms
6 ae-0-11.bar1.Tampa1.Level3.net (4.69.137.109) 15.208 ms 11.909 ms 12.375 ms
7 4.53.172.134 (4.53.172.134) 9.604 ms 9.141 ms 9.173 ms
8 one.one.one.one (1.0.0.1) 9.556 ms 9.600 ms 9.427 ms

Yes, 1.0.0.1 appears to be properly routed at this point. 1.1.1.1 still vanishes in their own network.

When I run this command I do get an interesting output though different from the others.

dig +tcp @1.1.1.1 id.server CH TXT
;; Connection to 1.1.1.1#53(1.1.1.1) for id.server failed: connection refused.