Bind not responding

Hello,

I have a router on my home network running Debian Woody. Last week I
started getting problems with Bind (Version 8.3.3) and it's been
getting worse since. I always have to try several times to get Bind to
resolve a network name. If I enter a URL into the browser on a machine
on the network and let it sit, Bind writes the following to named.log:

20-May-2004 17:27:20.851 queries: info:
XX+/192.168.0.250/slashdot.org/A/IN
20-May-2004 17:27:30.132 queries: info:
XX+/192.168.0.250/www.slashdot.org/A/IN
20-May-2004 17:27:31.132 queries: info:
XX+/192.168.0.250/www.slashdot.org/A/IN
20-May-2004 17:27:32.131 queries: info:
XX+/192.168.0.250/www.slashdot.org/A/IN
20-May-2004 17:27:34.131 queries: info:
XX+/192.168.0.250/www.slashdot.org/A/IN
20-May-2004 17:27:38.131 queries: info:
XX+/192.168.0.250/www.slashdot.org/A/IN

After that, the browser says "website not found". Only after I
repeatedly reload the page in the browser does it work.
Nothing in named.log, or syslog, or /var/log/messages indicates any
problems. I tried "ndc restart", but that didn't change anything.
What could be the reason for this strange behaviour and how do I fix
it?
Thanks,

Peter

On 20 May 2004 09:09:55 -0700, Peter Klein <der_benutzer@hotmail.com> wrote:
> Hello,
>
> I have a router on my home network running Debian Woody. Last week I
> started getting problems with Bind (Version 8.3.3) and it's been
> getting worse since. I always have to try several times to get Bind to
> resolve a network name. If I enter a URL into the browser on a machine
> on the network and let it sit, Bind writes the following to named.log:
>
> 20-May-2004 17:27:20.851 queries: info:
> XX+/192.168.0.250/slashdot.org/A/IN
> 20-May-2004 17:27:30.132 queries: info:
> XX+/192.168.0.250/www.slashdot.org/A/IN
> 20-May-2004 17:27:31.132 queries: info:
> XX+/192.168.0.250/www.slashdot.org/A/IN
> 20-May-2004 17:27:32.131 queries: info:
> XX+/192.168.0.250/www.slashdot.org/A/IN

Are you using forwarders (have you checked them to see if they respond
directly when specified in 'host' or 'nslookup' command)?

Is your root hints file up to date? They sometimes change and you need to
use dig on one of them occasionally to get fresh list of root servers.

--
David Efflandt - All spam ignored http://www.de-srv.com/