-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Guntner wrote on Thu, Dec 05, 2002 at 04:29:30PM -0800 :
>
> > So there are two name servers listed as authoritative for that domain.
> > But if you query them, both respond with "." domain entries, which are
> > the root dns entries. Since the
Todd Lyons grabbed a keyboard and wrote:
>
> David Guntner wrote on Thu, Dec 05, 2002 at 02:47:21PM -0800 :
> >
> > Of late, I've been getting TONS of "named: lame server resolving "
> > messages anytime a DNS lookup takes place locally. I've got the caching
> > nameserver package installed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Guntner wrote on Thu, Dec 05, 2002 at 02:47:21PM -0800 :
Content-Description: Mail message body
> Of late, I've been getting TONS of "named: lame server resolving "
> messages anytime a DNS lookup takes place locally. I've got the caching
This time "David Guntner" <[EMAIL PROTECTED]>
becomes daring and writes:
> Of late, I've been getting TONS of "named: lame server resolving "
> messages anytime a DNS lookup takes place locally. I've got the caching
> nameserver package installed, with BIND9. ML 9.0. Anyone have any ide
Of late, I've been getting TONS of "named: lame server resolving "
messages anytime a DNS lookup takes place locally. I've got the caching
nameserver package installed, with BIND9. ML 9.0. Anyone have any ideas
what would be causing this? My syslog is starting to get really
crowded
