bind not resolving localy

[David Botham]

Look in your /etc/resolv.conf file:

Is there a line like this:

nameserver <ip-of-second-name-server>

and if so, is it before one just like it for the first name server?

In other words, dig will use the name server listed here in the order
they are shown...


Dave...

> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> Behalf Of Kalin Mintchev
> Sent: Thursday, August 08, 2002 3:50 PM
> To: bind-users at isc.org
> Subject: bind not resolving localy
> 
> 
> 
> hi list,
> 
> i have a redhat 7.2 box with bind 9.1.3 on it.
> bind is running. the first nameserver on the machine is the same IP as
the
> machine itself. when i do dig for my.daomain.com the query defaults to
the
> second name server. if i force it to look on the same machine with dig
> @this.machine i get the right results.
> the logs don't log anything weird
> i can't find anything wrong with the named.conf..
> this wouldn't be a problem except it slows down the ftp, ssh and other
> sessions...
> also if i do ping to something.whatever.com i get huge dropouts, but
if i
> ping the same machine using the IP address the ping is fine...
> it seems to be somewhere on the resolving part but i can't figure it
out..
> 
> can somebody help?
> 
> thanks