Diagnosis help

[Kevin Darcy]

It resolves just fine for me. Both nameservers answer with the same correct
data.

What exactly do you mean by "not resolving", by the way? Are you getting
NXDOMAIN? NOERROR with 0 answer records? SERVFAIL? A timeout? Using
"dig" instead of nslookup helps to distinguish these different kinds of
errors.

If you're getting a "bad" response from somewhere, one way to track it is to
turn on host-statistics in your local caching nameserver and dump the cache
when the problem occurs. The dump will tell you where the bad answer came
from. You can also manually point your lookup tool to each of the
authoritative nameservers, but this doesn't help you if your local
nameserver is using forwarding or stub zones, etc.


- Kevin

Jon Booth wrote:

> My zone lucidlogic.com is having a problem with one of the hostnames.
>
> europa.lucidlogic.com is resolving here but ganymede.lucidlogic.com is
> not.
>
> Can anyone see why?
>
> How do I know which nameserver (primary or secondary) nslookup is getting
> its info from?
>
> Thanks for any help
> Jon
>
> $ORIGIN com.
> lucidlogic      IN      SOA     europa.lucidlogic.com.
> postmaster.jonbooth.com. (
>                 2001052402 7200 3600 6912000 7200 )
>                 IN      NS      europa.lucidlogic.com.
>                 IN      NS      ganymede.lucidlogic.com.
>                 IN      MX      50 europa.lucidlogic.com.
> $ORIGIN lucidlogic.com.
> europa             IN      A       144.132.2.3
> www             IN      A       144.132.2.3
> spanky          IN      A       144.132.2.3
> ganymede        IN      A       203.45.62.18
> callisto        IN      A       192.168.1.25
> io              IN      A       192.168.1.2