[outages] .us TLD issues?

[John Kinsella]

Seems cleared up. My monitoring systems weren't configured to traceroute to the resolvers, will have that fixed for next time...

John

On Aug 15, 2013, at 1:08 PM, "Smith, Donald" <Donald.Smith at CenturyLink.com> wrote:

> Working here where are you coming from?
> 
> 
> nslookup ibm.com b.cctld.us
> Server:    156.154.125.70
> Address 1: 156.154.125.70 b.cctld.us
> 
> Name:      ibm.com
> Address 1: 129.42.38.1 redirect.www.ibm.com
> 
> nslookup neustar.us neustart.us
> Server:    199.59.243.107
> Address 1: 199.59.243.107
> 
> Name:      neustar.us
> Address 1: 107.21.46.236 ec2-107-21-46-236.compute-1.amazonaws.com
> 
> 
> "Pampers use multiple layers of protection to prevent leakage. Rommel used defense in depth to defend European fortresses." (A.White) Donald.Smith at CenturyLink.com
> 
> 
>> -----Original Message-----
>> From: Outages [mailto:outages-bounces at outages.org] On Behalf Of John
>> Kinsella
>> Sent: Thursday, August 15, 2013 1:49 PM
>> To: outages at outages.org
>> Subject: [outages] .us TLD issues?
>> 
>> Been having issues resolving .us domains since about 12:20 Pacific from
>> Dallas/San Jose/San Francisco. Seems to be coming back slowly, DDOS
>> maybe?
>> 
>> $ nslookup neustar.us
>> ;; connection timed out; trying next origin ;; connection timed out; no
>> servers could be reached
>> 
>> $ whois neustar.us
>> [Querying whois.nic.us]
>> [whois.nic.us: Temporary failure in name resolution] [Unable to connect
>> to remote host]
>> 
>> 
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org
>> https://puck.nether.net/mailman/listinfo/outages