Error Msg

Barry Margolin barmar at genuity.net
Tue Apr 25 17:15:32 UTC 2000


In article <8e3j85$1v1t$1 at wrath.news.nacamar.de>,
Christoph Klempau <klempau at sunflowers.de> wrote:
>Hi!
>
>I got an unknow error msg in my logs:
>
>Apr 25 09:13:14 XXXX named[1130]: sysquery: findns error (NXDOMAIN) on
>195.185.213.40.181.63.195.in-addr.arpa?
>Apr 25 09:13:14 XXXX named[1130]: sysquery: findns error (NXDOMAIN) on
>195.63.181.1.181.63.195.in-addr.arpa?
>Apr 25 09:13:14 XXXX named[1130]: sysquery: findns error (NXDOMAIN) on
>212.172.106.1.181.63.195.in-addr.arpa?
>
>Any ideas where the problem is located!?

The 181.63.195.in-addr.arpa zone file probably contains something like:

<something>  IN NS  195.185.213.40
<something>  IN NS  195.63.181.1
<something>  IN NS  212.172.106.1

NS records are supposed to point to hostnames, not IP addresses.  And since
there's no "." at the end of those lines, they get the zone name appended
to them.

However, I just did a zone transfer of that domain, and didn't see records
like these, so I'm not really sure where they are.  I notice that you have
RFC 2317 delegation of the 195.63.181.0/25 subnet, but the subzone doesn't
exist on your servers.  Perhaps the problem is in the files for that
subzone, and it's resulting in both these errors and the zone not existing.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.



More information about the bind-users mailing list