Re: Re: still can't resolve...

[Pollywog <pollywog@shadypond.com>]

On 08-Oct-99 Ben Lutgens wrote:
> Next I would tail -f some various log files, hell try em all while you
> attempt
> to get some name service. I must say that I am intruiged what may be the
> cause. What version of bind are you running. Did you check bugs.debian.org
> for
> a possible bug in there. There is twwo parts of bind you know, the client
> side
> is called the resolver (herein lies your problem I believe) This is why I
> say
> to really eye-fsck bind. Hope this helps.

I also had trouble with BIND after an upgrade; the startup scripts would no
longer work.  I had to add the startup to /etc/init.d/network to get BIND to
start when I reboot the machine.

Also, 'ndc restart' no longer works.

I had a similar problem with BIND when I was using OpenLinux.



--
Andrew