1 edit | reply to jsn_oldp
Re: [AZ] usajobs.gov lookup problems on Cox DNS servers 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 |
| 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 |
