DNS issue and client section gone missing

**Ron** · 10-22-2006, 07:57 PM

If anybody out there can access the ticket system, could you kindly open an emergency ticket regarding DNS resolution and point them to this thread, and to my previous ticket number 2386558

Thanks.

**Ron** · 10-22-2006, 08:02 PM

I've had a ticket open since Friday on a DNS issue that is affecting my website in a minor way functionally, but is a major hassle administratively.

The ticket has been escalated, and of course I know what that means on a Friday night, it's likely I won't see any help until Monday.

Sure enough it wasn't fixed by yesterday (Saturday) (in fact my response to the escalation was still sitting in "New" status, meaning the resource to which this was escalated hadn't yet read the ticket.

OK, I understand people can have a weekend.

Anyway, this morning I log in and find that at some point the problem has been fixed, although I don't have a ticket update about it. I was pleasantly surprised.

Now the issue is back, so I go to log into the ticket system, and the client section of jaguarpc.com is missing....

Anhyone else having code failing/taking forever/timing out doing any DNS resolution from their server?

Code:

$ time wget google.com
--21:26:48--  http://google.com/
           => `index.html'
Resolving google.com... failed: Temporary failure in name resolution.

real    1m20.011s
user    0m0.001s
sys     0m0.002s

$ time wget google.com
--21:39:17--  http://google.com/
           => `index.html'
Resolving google.com... failed: Temporary failure in name resolution.

real    1m20.022s
user    0m0.001s
sys     0m0.002s

$ time dig google.com

; <<>> DiG 9.2.4 <<>> google.com
;; global options:  printcmd
;; connection timed out; no servers could be reached

real    0m12.056s
user    0m0.003s
sys     0m0.002s

Maybe there's serious DNS issues going on... I can't resolve another domain that's hosted at JAG.... sigh.

**dwannall** · 10-22-2006, 08:03 PM

Yea, I just posted the same thing. It's gotta be bad if www.jaguarpc.com was down. -Doug

**Ron** · 10-22-2006, 08:09 PM

I am seeing that www.dnsstuff.com and www.dnsreport.com are also failing, and they're hosted in Washington, DC.

Could be a coincidence?

**Ron** · 10-22-2006, 08:11 PM

If anybody out there can access the ticket system, could you kindly open an emergency ticket regarding DNS resolution and point them to this thread, and to my previous ticket number 2386558

Thanks.

**jaquestati** · 10-22-2006, 08:24 PM

i was able to login and start a ticket and reference this for you.

all my servers are down but jagpc is finally up again (obviously

what the h is goin on?

**the_ancient** · 10-22-2006, 08:29 PM

no go for me.

is the JPC client in houston still or GA?

My guess GA, after all that is "rock solid super fast" network you guys are raving about right

**ad_hoc** · 10-22-2006, 08:29 PM

It's been down for at least a half an hour. It just came back, then went down, then came back again.

This isn't funny.

**the_ancient** · 10-22-2006, 08:30 PM

just came back for me tooo....

**the_ancient** · 10-22-2006, 08:30 PM

Originally Posted by Ron

I am seeing that www.dnsstuff.com and www.dnsreport.com are also failing, and they're hosted in Washington, DC.

Could be a coincidence?

Both of them still work for me, all traces from them, and from me locally fail though

**Ron** · 10-22-2006, 08:35 PM

Great, we got timestamp issues on this forum now again, too.

OK, this forum went away for me for a while... back now (also obviously...)

Ancient, you're not seeing this?

Code:

http://www.dnsstuff.com/tools/lookup...gle.com&type=A
How I am searching:
Searching for google.com A record at j.root-servers.net [192.58.128.30]: Error: Socket error #10055 sendtoing UDP DNS socket..

Answer:
An error occurred: Socket error #10055 sendtoing UDP DNS socket..

Details:
I could not get to the nameserver authoritative for google.com.  Sorry!

or this:

Code:

http://www.dnsreport.com/tools/dnsre...ain=google.com
DNS Report for google.com
Generated by www.DNSreport.com at 02:28:40 GMT on 23 Oct 2006.


[A crash occurred, sorry -- ending gracefully]