On Tue, Aug 27, 2013 at 03:11:58PM -0700, Curtis Doty wrote:
Think NYT is trying to regain control back but forgot their glue. :-(
nytimes.com. 172800 IN NS dns.ewr1.nytimes.com. nytimes.com. 172800 IN NS dns.sea1.nytimes.com. ;; Received 107 bytes from 192.48.79.30#53(j.gtld-servers.net) in 121 ms
dig: couldn't get address for 'dns.ewr1.nytimes.com': not found
What server did you query? If you're using the cached NS records for nytimes.com, ...
dig @a.gtld-servers.net www.nytimes.com
;; AUTHORITY SECTION: nytimes.com. 2D IN NS dns.ewr1.nytimes.com. nytimes.com. 2D IN NS dns.sea1.nytimes.com. ;; ADDITIONAL SECTION: dns.ewr1.nytimes.com. 2D IN A 170.149.168.134 dns.sea1.nytimes.com. 2D IN A 170.149.173.133 But from my caching server:
dig NS nytimes.com
;; QUESTION SECTION: ;nytimes.com. IN NS ;; ANSWER SECTION: nytimes.com. 76063 IN NS ns2.syrianelectronicarmy.com. nytimes.com. 76063 IN NS ns1.syrianelectronicarmy.com.
dig @ns1.syrianelectronicarmy.com dns.sea1.nytimes.com
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 351 -- Brett