Diagnosis help

[Jon Booth]

That server seems to have come good. It is the primary nameserver (at the
top of my /etc/resolv.conf) for my ISP.
I tried
dig lucidlogic.com @badserver
which returned an old zone update which should have expired.
and also 
nslookup ganymede.lucidlogic.com badsersver
which could not resolve. Funnily enough it could resolve europa which I
added around the same time which confuses me.

Anyway perhaps it connections dropped out at vital times but it is good
now. It has been useful to see how to diagnose. thanks

Jon

On Tue, 29 May 2001, Chris Buxton wrote:

> 
> I am unable to find a problem from the outside. Therefore, you'll 
> have to do some investigation to find out the source of the problem.
> 
> I queried a gTLD server (f.gtld-servers.net, as it happens) and found 
> exactly what I expected:
> 
> lucidlogic.com.			NS	ganymede.lucidlogic.com.
> lucidlogic.com.			NS	europa.lucidlogic.com.
> ganymede.lucidlogic.com.	A	203.45.62.18
> europa.lucidlogic.com.		A	144.132.2.3
> 
> Querying both of these servers yielded similar results. Each server 
> knows the NS records for the zone and the A records for the servers; 
> each answer is authoritative.
> 
> So, the questions for you to answer are:
> 
> - What machine can't find ganymede.lucidlogic.com?
> - Is that machine using Windows, Mac OS, or something Unix-like?
> - If it's Unix-like, what DNS resolvers are listed in its 
> configuration? It may be getting bad data from any of them.
> - If it's Windows or Mac OS, what is the first DNS resolver listed in 
> its configuration? It only queries the first listed resolver unless 
> that resolver doesn't answer.
> 
> Use iterative (nonrecursive) queries to find out what DNS resolver 
> has bad data. If the response is authoritative, then the resolver 
> thinks that it is authoritative, and its zone file is probably 
> incorrect. If the response is non-authoritative, clear the server's 
> cache and send it a recursive query; does it come up with the bad 
> answer again?
> 
> If no resolver seems to have bad data (some sort of data, either 
> cached or authoritative, that either indicates that 
> ganymede.lucidlogic.com doesn't exist or that it has some incorrect 
> IP address), then perhaps the answer is to just retry. Or perhaps one 
> of your resolvers is unable to resolve properly.
> 
> I hope this helps.
> ____________________________________________________________________
> 
> Chris Buxton <cbuxton at menandmice.com>
> 
> Men & Mice <http://www.menandmice.com/> provides:
>   - DNS training, including Active Directory
>   - QuickDNS, a DNS management system for Bind on Linux & Mac OS
>     (Solaris support coming soon!)
>   - DNS Expert, a DNS analysis and troubleshooting utility
> ____________________________________________________________________
> 
> At 10:47 AM +1000 5/30/01, 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
> 
>