jsn_oldp
@cox.net
|  [AZ] usajobs.gov lookup problems on Cox DNS servers
Hi all,
In the last few weeks, I've been having trouble doing lookups on the usajobs.gov domain when using a Cox nameserver. The problem first appeared when browsing that site on the web; sometimes the lookup would work, other times it would be slow, and it would often fail completely. I've experienced this using Firefox, IE, and on different computers entirely, so I think I can rule out software problems.
Now I've done some exploration with dig. My router gets assigned 3 nameservers: 68.105.28.12, 68.105.29.12, and 68.105.28.11. If I use dig to query www.usajobs.gov all of these directly, I usually get "connection timed out; no servers could be reached". But if I query a different domain with the same servers, there are no problems. If I query usajobs.gov at a non-Cox nameserver (like 128.196.188.95), the lookup succeeds normally.
So as best as I can judge, Cox's nameservers are having a problem with the usajobs.gov domain, and they've only had the problem for a few weeks. Anybody have any advice on how to proceed from here?
-JSN |
|
Guzzler
join:2002-09-24
Tempe, AZ
| If you have already gotten an IP address from another DNS, you can always put that information into your HOSTS file.
If you are using XP go to:
C:\WINDOWS\system32\drivers\etc
to find the HOSTS file and enter the IP and host name.
I know, it's a kludge. But it will get you there. |
|
jsn_oldp
@cox.net
| Thanks, but using the IP address directly doesn't work (try it). I'm not sure why, but it might be related to the fact that monster.com (the contractor for usajobs) is an "Akamaized" site.
And like you say, that's a kludge. If it's a problem with Cox, it'll be for them to fix. It could also be a problem with monster.com, though. I don't know how to determine which.
Incidentally, I also did my dig queries from a completely non-Cox network, and got the same results. So being on the Cox network doesn't seem to factor in to this.
-JSN |
|
Guzzler
join:2002-09-24
Tempe, AZ
1 edit | said by jsn_oldp :
Incidentally, I also did my dig queries from a completely non-Cox network, and got the same results. So being on the Cox network doesn't seem to factor in to this.
-JSN
AAaaaaaaaaaaa. There is your answer. Something is amiss on the other end, with www.usajobs.gov |
|
jsn_oldp
@cox.net
| I'm not convinced that this shows it's usajobs.gov. I meant that I queried *Cox's* nameservers from a non-Cox network, just to rule out the freakish possibility that the originator of the DNS query was relevant to this problem. And I think I ruled it out. The problem still remains, though: 68.105.28.12, 68.105.29.12, and 68.105.28.11 (all Cox DNS servers) fail out when querying anything at usajobs.gov, but *seven* other non-Cox DNS servers that I tried have no trouble at all. In fact this evidence strongly suggests to me that it *isn't* usajobs that's the problem, which is why I posted here. If usajobs.gov really did have a problem, why would only Cox nameservers expose it?
I apologize if I haven't been explicit enough about what the issue is. I'm going to put in a tech support email to both Cox and usajobs.gov.
-JSN |
|
needforspeed59
Cruise Ship Just Passing Through
join:2001-05-02
Glendale, AZ | reply to jsn_oldp
I can get to it from Glendale.
--
Great success! High five! |
|
jsn_oldp
@cox.net | What nameserver are you querying?
-JSN |
|
