Re: [dns-operations] Looks like .us has a FAIL

2012-11-09 Thread Doug Barton
If you want to start a new thread, please don't reply to an old message and change the subject line. It causes your message to be "misfiled" for those who use clients that thread messages properly. The easiest way to start a new thread is to save the e-mail address of the list, and then create a n

Re: [dns-operations] Looks like .us has a FAIL

2012-11-09 Thread Fred Morris
On Fri, 9 Nov 2012, Fred Morris wrote: > demeter:~ demeter$ dig co.pierce.wa.us +trace ... > us. 172800 IN NS b.cctld.us. > us. 172800 IN NS a.cctld.us. > us. 172800 IN NS c.cctld.us. > us. 1728

Re: [dns-operations] Looks like .us has a FAIL

2012-11-09 Thread Jeroen Massar
On 2012-11-09 09:28, Fred Morris wrote: > > demeter:~ demeter$ dig co.pierce.wa.us +trace [..] > ;; connection timed out; no servers could be reached It could be transient, or, more likely: you can't reach the nameservers. You might want to do a traceroute to them to see where that goes wrong.

Re: [dns-operations] Looks like .us has a FAIL

2012-11-09 Thread Stephane Bortzmeyer
On Fri, Nov 09, 2012 at 01:28:32AM -0700, Fred Morris wrote a message of 37 lines which said: > ;; connection timed out; no servers could be reached Works for me, from several places: % check-soa us c.cctld.us. : 156.154.127.70 (2008314055) k.cctld.us. : 156.154.128.70 (2008314055) 2001:5

[dns-operations] Looks like .us has a FAIL

2012-11-09 Thread Fred Morris
demeter:~ demeter$ dig co.pierce.wa.us +trace ; <<>> DiG 9.6-ESV-R4-P3 <<>> co.pierce.wa.us +trace ;; global options: +cmd . 32005 IN NS k.root-servers.net. . 32005 IN NS l.root-servers.net. . 32005 IN