Looks to have mostly cleared for us. On Thu, Apr 3, 2014 at 9:44 PM, Bill Fehring <bill@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