Single domain fails lookup

[jim at coam.net]

I am having the same kind of problem with this domain: omniairintl.com
with dig @dns.coam.net omniairintl.com
i get a SERVFAIL id: 6
interestingly, i have the same results from my secondary dns, ns1.espire.net

but, if I use other nameservers (say, ns.utah.edu, or their nameservers,
ns1.netaxs.net or ns2....) the lookup is successful....

so far, i have found no other domains like that, and my hints/root-servers file
seems to be "fine" ... at least it seems to function for other lookups...

is there some widespread, but "intermittent" problem that anyone is aware of?
does anyone have any ideas about where to start trying to fix this?

thanks!!

In article <3985E1E4.78361BAB at daimlerchrysler.com>, Kevin says...
>
>
>Bob Dozier wrote:
>
>> There is domain 'utpb.edu' that will fail to resolve an address when our
>> customers attempt to get to the site. All other domains will get an
>> address resolved with our DNS. The 'utpb.edu' domain will continue to
>> fail until we restart DNS services. This domain is not in our DNS system.
>> This has happened with this domain on several occasions. Is it something
>> I can control or is it something the system admin of that domain needs to
>> address? Thanks!
>
>I can resolve that just fine right now, and a quick check of the domain
>reveals no obvious problems. It's difficult to troubleshoot a problem that
>doesn't appear to exist.
>
>Next time this happens, why don't you try running some queries manually --
>query the name itself, then do an NS query of the domain, an A query of each
>of the nameservers listed for the domain, then repeat all 3 of those queries
>*to* each those nameservers? The results of those queries should probably
>help narrow down the problem.
>
>
>- Kevin
>
>
>
>
>