Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bind Error's

0 views
Skip to first unread message

Jim Reid

unread,
Jun 5, 1998, 3:00:00 AM6/5/98
to

>>>>> "Syd" == Syd Alsobrook <also...@onsyd.com> writes:

Syd> Jun 3 15:30:02 naiad named[4911]: sysquery: findns error (3) on 190.160.32.15.foo.com?

There is a badly broken NS record in the foo.com zone.

And here it is:

Syd> ; BIND data file for foo.com
Syd> foo.com. IN NS 190.160.32.15

This should be:
foo.com. IN NS naiad.foo.com.

assuming that naiad is set up as a nameserver for this domain. Because
you put a dotted decimal string there and didn't dot terminate it, the
nameserver appended the current domain name to the RR, which made it
load an NS record of:
foo.com. IN NS 190.160.32.15.foo.com.
which of course doesn't exist and causes the nameserver to print the
error message above.

BTW, you should have at least 2 NS records (ie at least 2 nameservers)
for your domains. One of these should be off-site, so there's no
single point of failure for DNS lookups for your domain. Also, you
really should use the YYYYMMDDVV convention for the serial number in
the SOA record. This can be a big help when debugging.

0 new messages