non-authoritative zone (NOTAUTH) problem in bind on debian

[Kevin Darcy]

"David A. Cornelson" wrote:

> "David A. Cornelson" <dave at plover.net> wrote in message
> news:aj6aka$26r3$1 at isrv4.isc.org...
> > I have over 50 domains in my linux dns setup. This is the primary dns. I
> > also second all of these domains on a win2k/.net server. I've never had a
> > problem until now.
> >
> > I have two domains, rdocuments.com and overthehillfarm.net that won't
> update
> > on the secondary server. The syslog entries are:
> >
> > Aug 11 11:15:47 zork named[188]: client 64.81.228.30#1557: bad zone
> transfer
> > request: 'rdocuments.com/IN': non-authoritative zone (NOTAUTH)
> > Aug 11 11:16:47 zork named[188]: client 64.81.228.30#1558: bad zone
> transfer
> > request: 'overthehillfarm.net/IN': non-authoritative zone (NOTAUTH)
> >
>
> I rolled back bind to version 8 (i had bind9 in there) and now all my
> domains transfer to my .net server without a hitch. I don't understand what
> could have been happening in bind9 that was causing a problem, but it all
> works fine now.

You're not going to be able to stay at BIND 8 forever, so you might want to
try and diagnose the root cause of this problem, rather than just working
around it. Looking back at your old messages, I see that the NOTAUTH errors
are dated August 11, but the log messages showing a clean load of
rdocuments.com and overthehillfarm.net are dated August 12. Are you absolutely
sure you were still having the same problem after the zone started loading
cleanly? Or could it have been some other kind of problem (e.g. a setting on
the client side) that was coincidentally fixed by downgrading to BIND 8?


- Kevin