Strange results with dig, this one is wacky!

[Barry Margolin]

In article <a4kil6$kk2 at pub3.rc.vix.com>,
Kevin Darcy  <kcd at daimlerchrysler.com> wrote:
>I don't understand what you mean "not going to the main nameservers". The
>name resolves fine when you point dig at the "main nameservers", right? It
>returns SERVFAIL when you point it at your local nameserver, right? The
>problem is your local nameserver. As I said, look in the logs to see what is
>wrong. Or, check your firewall/NAT configuration (presumably you're using a
>firewall and/or NAT since 192.168.1.2 is a private address) and/or routing
>configuration to verify that your nameserver can communicate with Internet
>nameservers.

A caching server returns SERVFAIL if it times out trying to query the
authoritative servers.

This could be due to a firewall problem, as you say.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.