[outages] Level(3) Anycast DNS down in SF Bay Area?

Cb B cb.list6 at gmail.com
Fri Apr 4 00:58:37 EDT 2014


On Thu, Apr 3, 2014 at 9:44 PM, Bill Fehring <bill at zscaler.com> wrote:
> So I've tried from a few different networks in the SF Bay Area and
> Level(3)'s anycast DNS servers seem to be having trouble resolving anything.
>
> 4.2.2.1 through 6, and 209.244.0.3 and 4
>
> % dig @4.2.2.2 google.com
>
> ; <<>> DiG 9.5.1-P3 <<>> @4.2.2.2 google.com
> ; (1 server found)
> ;; global options:  printcmd
> ;; connection timed out; no servers could be reached
>
> They do still seem to have root hints though.
>
> % dig @4.2.2.2
>
> ; <<>> DiG 9.5.1-P3 <<>> @4.2.2.2
> ; (1 server found)
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61287
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;. IN NS
>
> ;; ANSWER SECTION:
> . 18209 IN NS d.root-servers.net.
> . 18209 IN NS i.root-servers.net.
> . 18209 IN NS l.root-servers.net.
> . 18209 IN NS h.root-servers.net.
> . 18209 IN NS b.root-servers.net.
> . 18209 IN NS c.root-servers.net.
> . 18209 IN NS k.root-servers.net.
> . 18209 IN NS m.root-servers.net.
> . 18209 IN NS e.root-servers.net.
> . 18209 IN NS g.root-servers.net.
> . 18209 IN NS f.root-servers.net.
> . 18209 IN NS a.root-servers.net.
> . 18209 IN NS j.root-servers.net.
>
> ;; Query time: 1 msec
> ;; SERVER: 4.2.2.2#53(4.2.2.2)
> ;; WHEN: Thu Apr  3 21:38:51 2014
> ;; MSG SIZE  rcvd: 228
>
> --Bill Fehring
>

Yep, down in Seattle from Comcast

cbyrne at odie ~ $ dig @4.2.2.2 google.com

; <<>> DiG 9.9.2-P1 <<>> @4.2.2.2 google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
cbyrne at odie ~ $ dig @4.2.2.1 google.com

; <<>> DiG 9.9.2-P1 <<>> @4.2.2.1 google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
cbyrne at odie ~ $ dig @4.2.2.1

; <<>> DiG 9.9.2-P1 <<>> @4.2.2.1
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50918
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;. IN NS

;; ANSWER SECTION:
. 23526 IN NS a.root-servers.net.
. 23526 IN NS b.root-servers.net.
. 23526 IN NS c.root-servers.net.
. 23526 IN NS d.root-servers.net.
. 23526 IN NS e.root-servers.net.
. 23526 IN NS f.root-servers.net.
. 23526 IN NS g.root-servers.net.
. 23526 IN NS h.root-servers.net.
. 23526 IN NS i.root-servers.net.
. 23526 IN NS j.root-servers.net.
. 23526 IN NS k.root-servers.net.
. 23526 IN NS l.root-servers.net.
. 23526 IN NS m.root-servers.net.

;; Query time: 36 msec
;; SERVER: 4.2.2.1#53(4.2.2.1)
;; WHEN: Thu Apr  3 21:56:37 2014
;; MSG SIZE  rcvd: 239

cbyrne at odie ~ $ traceroute 4.2.2.1

 3  te-0-2-0-14-ur07.seattle.wa.seattle.comcast.net (68.86.98.33)
32.154 ms  32.151 ms  32.147 ms
 4  ae-20-0-ar03.burien.wa.seattle.comcast.net (69.139.164.125)
35.020 ms  34.992 ms  35.003 ms
 5  ae-20-0-ar03.seattle.wa.seattle.comcast.net (69.139.164.129)
32.065 ms ae-1-0-ar03.seattle.wa.seattle.comcast.net (68.85.240.94)
61.769 ms  61.718 ms
 6  he-1-3-0-0-11-cr01.seattle.wa.ibone.comcast.net (68.86.93.169)
34.961 ms he-1-4-0-0-10-cr01.seattle.wa.ibone.comcast.net
(68.86.94.237)  11.296 ms
he-1-7-0-0-11-cr01.seattle.wa.ibone.comcast.net (68.86.93.5)  15.231
ms
 7  4.68.63.65 (4.68.63.65)  40.566 ms  43.059 ms  43.010 ms
 8  ae-31-51.ebr1.Seattle1.Level3.net (4.69.147.150)  42.909 ms
42.898 ms  42.887 ms
 9  ae-7-7.ebr2.SanJose1.Level3.net (4.69.132.49)  42.814 ms  42.741
ms  42.764 ms
10  ae-92-92.csw4.SanJose1.Level3.net (4.69.153.30)  42.634 ms
ae-82-82.csw3.SanJose1.Level3.net (4.69.153.26)  42.645 ms
ae-92-92.csw4.SanJose1.Level3.net (4.69.153.30)  45.764 ms
11  ae-4-90.edge1.SanJose1.Level3.net (4.69.152.206)  45.714 ms
45.661 ms ae-1-60.edge1.SanJose1.Level3.net (4.69.152.14)  37.083 ms
12  a.resolvers.level3.net (4.2.2.1)  36.307 ms  39.875 ms  39.795 ms


> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>



More information about the Outages mailing list