Google DNS apparently down for a lot of Brazilians
111 views
Skip to first unread message
jsv...@it.eng.br
Jun 14, 2017, 4:07:36 PM6/14/17
to public-dns-discuss
Hello,
At about Jun 14 17:00 UTC, our DNS server (which uses 8.8.8.8 8.8.4.4 as forwarders) started responding erratically. I traced it down to google DNS servers responding too slow, then not responding at all.
Checked downdetector, and it seems to be for Brazil only:
Here are some test results:
I can ping 8.8.8.8/8.8.4.4:
yankee:/etc/bind# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=58 time=14.7 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=58 time=15.4 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=58 time=14.8 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 14.738/14.991/15.407/0.328 ms
yankee:/etc/bind# ping 8.8.4.4
PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.
64 bytes from 8.8.4.4: icmp_seq=1 ttl=58 time=14.7 ms
64 bytes from 8.8.4.4: icmp_seq=2 ttl=58 time=15.0 ms
64 bytes from 8.8.4.4: icmp_seq=3 ttl=58 time=14.6 ms
Traceroute gets there:
yankee:/etc/bind# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 131.255.236.161 (131.255.236.161) 0.560 ms 0.670 ms 0.665 ms
2 rcoresjc11-ae-0.horizonstelecom.com.br (177.124.56.74) 1.110 ms 1.067 ms 1.048 ms
3 rcoreoco11-xe1-2-0.horizonstelecom.com.br (177.124.56.81) 3.665 ms 3.776 ms 3.768 ms
4 ritxoco21-xe0-2-0.horizonstelecom.com.br (177.124.56.41) 3.993 ms 3.977 ms 3.953 ms
5 ritxcta51-xe0-2-1.horizonstelecom.com.br (177.124.56.82) 9.142 ms 9.279 ms 9.279 ms
6 as15169.saopaulo.sp.ix.br (187.16.218.58) 15.197 ms 14.518 ms 14.616 ms
7 108.170.245.129 (108.170.245.129) 14.733 ms 108.170.245.161 (108.170.245.161) 15.106 ms 108.170.245.129 (108.170.245.129) 14.805 ms
8 216.239.56.59 (216.239.56.59) 15.143 ms 216.239.56.61 (216.239.56.61) 15.201 ms 216.239.56.59 (216.239.56.59) 15.085 ms
9 google-public-dns-a.google.com (8.8.8.8) 14.813 ms 14.811 ms 14.895 ms
But using a google DNS:
yankee:/etc/bind# dig @8.8.8.8 google.com
; <<>> DiG 9.9.5-9+deb8u11-Debian <<>> @8.8.8.8 google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
Using a Level3 DNS:
yankee:/etc/bind# dig @4.2.2.2 google.com
; <<>> DiG 9.9.5-9+deb8u11-Debian <<>> @4.2.2.2 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22636
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 53 IN A 216.58.194.78
;; Query time: 137 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Wed Jun 14 15:23:47 -03 2017
;; MSG SIZE rcvd: 44
Or our server (now using root servers):
yankee:/etc/bind# dig @localhost google.com
; <<>> DiG 9.9.5-9+deb8u11-Debian <<>> @localhost google.com
; (3 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48367
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 5
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 300 IN A 216.58.202.46
;; AUTHORITY SECTION:
google.com. 168506 IN NS ns4.google.com.
google.com. 168506 IN NS ns3.google.com.
google.com. 168506 IN NS ns2.google.com.
google.com. 168506 IN NS ns1.google.com.
;; ADDITIONAL SECTION:
ns1.google.com. 343040 IN A 216.239.32.10
ns2.google.com. 343040 IN A 216.239.34.10
ns3.google.com. 343040 IN A 216.239.36.10
ns4.google.com. 343040 IN A 216.239.38.10
;; Query time: 142 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jun 14 15:22:10 -03 2017
;; MSG SIZE rcvd: 191
Regards,
Joao S Veiga
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages