Looks like more than just m root servers. >From a handful of Catchpoint monitoring nodes in Beijing.
http://p.catchpoint.com/ui/Entry/PW/I/DFl-tau-Ie-I301-jR.BWB_P8Lf-AV0AR0-jR.BWB_P8Lf-tau (Beijing, CN - AWS, got response directly from h.gtld-servers.net<http://h.gtld-servers.net>) http://p.catchpoint.com/ui/Entry/PW/I/DFl-tau-HQ-I316-jR.BWB_QiRB-AV0AR0-jR.BWB_QiRB-tau (Beijing, CN - CERNET, got response directly from k.gtld-servers.net<http://k.gtld-servers.net>) http://p.catchpoint.com/ui/Entry/PW/I/DFl-tau-HB-I316-jR.BWB_QiRB-AV0AR0-jR.BWB_QiRB-tau (Bejing, CN - China Mobile, got response directly from b.gtld-servers.net<http://b.gtld-servers.net>) http://p.catchpoint.com/ui/Entry/PW/I/DFl-tau-BH-I316-jR.BWB_QiRB-AV0AR0-jR.BWB_QiRB-tau (Beijing, CN - Telecom, got response directly from h.gtld-servers.net<http://h.gtld-servers.net>) http://p.catchpoint.com/ui/Entry/PW/I/DFl-tau-GU-I316-jR.BWB_QiRB-AV0AR0-jR.BWB_QiRB-tau (Beijing, CN - Unicom, got response directly from g.gtld-servers.net<http://g.gtld-servers.net>) --- // Shawn On Jan 8, 2015, at 8:37 AM, Shawn Hsiao <[email protected]<mailto:[email protected]>> wrote: We have reports that some qnames are not resolving properly in China, and in two of the follow ups I have received it appears they are getting random responses directly from the m root server. Not sure what is causing it, but I am wondering if someone on the list knows. So far, I am only aware this happening to edgecastcdn.net<http://edgecastcdn.net/> domain, and other domains we tested are resolving fine. Thanks. (from a home computer) $ dig +trace cs216.wpc.edgecastcdn.net<http://cs216.wpc.edgecastcdn.net/> ; <<>> DiG 9.8.3-P1 <<>> +trace cs216.wpc.edgecastcdn.net<http://cs216.wpc.edgecastcdn.net> ;; global options: +cmd . 23964 IN NS j.root-servers.net<http://j.root-servers.net>. . 23964 IN NS i.root-servers.net<http://i.root-servers.net>. . 23964 IN NS g.root-servers.net<http://g.root-servers.net>. . 23964 IN NS f.root-servers.net<http://f.root-servers.net>. . 23964 IN NS m.root-servers.net<http://m.root-servers.net>. . 23964 IN NS h.root-servers.net<http://h.root-servers.net>. . 23964 IN NS e.root-servers.net<http://e.root-servers.net>. . 23964 IN NS c.root-servers.net<http://c.root-servers.net>. . 23964 IN NS a.root-servers.net<http://a.root-servers.net>. . 23964 IN NS l.root-servers.net<http://l.root-servers.net>. . 23964 IN NS k.root-servers.net<http://k.root-servers.net>. . 23964 IN NS b.root-servers.net<http://b.root-servers.net>. . 23964 IN NS d.root-servers.net<http://d.root-servers.net>. ;; Received 228 bytes from 192.168.1.1#53(192.168.1.1) in 12 ms cs216.wpc.edgecastcdn.net<http://cs216.wpc.edgecastcdn.net>. 2732 IN A 206.17.103.24 ;; Received 84 bytes from 202.12.27.33#53(202.12.27.33) in 100 ms (from a server in a datacenter) $ dig +trace cs216.wpc.edgecastcdn.net<http://cs216.wpc.edgecastcdn.net/> ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.4 <<>> +trace cs216.wpc.edgecastcdn.net<http://cs216.wpc.edgecastcdn.net> ;; global options: +cmd . 498401 IN NS b.root-servers.net<http://b.root-servers.net>. . 498401 IN NS i.root-servers.net<http://i.root-servers.net>. . 498401 IN NS c.root-servers.net<http://c.root-servers.net>. . 498401 IN NS a.root-servers.net<http://a.root-servers.net>. . 498401 IN NS l.root-servers.net<http://l.root-servers.net>. . 498401 IN NS j.root-servers.net<http://j.root-servers.net>. . 498401 IN NS e.root-servers.net<http://e.root-servers.net>. . 498401 IN NS m.root-servers.net<http://m.root-servers.net>. . 498401 IN NS g.root-servers.net<http://g.root-servers.net>. . 498401 IN NS k.root-servers.net<http://k.root-servers.net>. . 498401 IN NS h.root-servers.net<http://h.root-servers.net>. . 498401 IN NS d.root-servers.net<http://d.root-servers.net>. . 498401 IN NS f.root-servers.net<http://f.root-servers.net>. ;; Received 508 bytes from 192.168.4.192#53(192.168.4.192) in 8419 ms cs216.wpc.edgecastcdn.net<http://cs216.wpc.edgecastcdn.net>. 1911 IN A 54.210.250.207 ;; Received 59 bytes from 202.12.27.33#53(202.12.27.33) in 3 ms --- // Shawn
_______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
