8.2.3: no addrs found for root NS
Kevin Darcy
kcd at daimlerchrysler.com
Tue Oct 9 21:40:39 UTC 2001
Looks like you have bogus information in your hints file ("NS1", "NS2", etc.).
If you're not going to populate your hints file with proper information, then
don't even bother creating a hints zone definition -- either define
"global" forwarding or use the compiled-in set of hints.
-Kevin
Christian Hammers wrote:
> Hello
>
> I'm getting this errors nearly every day at random times but mainly when
> no server load but only some cronjobs (loganalyser etc) are running.
> The db.root file is up to date (1997082200 from Aug 22, 1997).
>
> Any ideas?
>
> bye,
>
> -christian-
>
> On Sun, Oct 07, 2001 at 02:02:04AM +0200, root wrote:
> > Unusual System Events
> > =-=-=-=-=-=-=-=-=-=-=
> > Oct 7 01:16:33 XX named[140]: sysquery: no addrs found for root NS ()
> > Oct 7 01:16:33 XX named[140]: sysquery: no addrs found for root NS (NS1)
> > Oct 7 01:16:33 XX named[140]: sysquery: no addrs found for root NS (NS2)
> > Oct 7 01:16:33 XX named[140]: sysquery: no addrs found for root NS (NS3)
> > Oct 7 01:56:18 XX named[140]: sysquery: no addrs found for root NS ()
> > Oct 7 01:56:18 XX named[140]: sysquery: no addrs found for root NS (NS1)
> > Oct 7 01:56:18 XX named[140]: sysquery: no addrs found for root NS (NS2)
> > Oct 7 01:56:18 XX named[140]: sysquery: no addrs found for root NS (NS3)
>
> --
> Christian Hammers WESTEND GmbH - Aachen und Dueren Tel 0241/701333-0
> ch at westend.com Internet & Security for Professionals Fax 0241/911879
> WESTEND ist CISCO Systems Partner - Premium Certified
More information about the bind-users
mailing list