errors with 8.2.3

Jim Reid jim at rfc1035.com
Mon Jan 29 23:00:13 UTC 2001


>>>>> "arie" == arie  <av3 at xs4all.nl> writes:

    arie> i just upped to 8.2.3 (chrooted Red Hat Linux), and on
    arie> starting bind it tells me my zonefiles (all of them) are not
    arie> ok. I ran 8.2.2-P5 and all went well. Here's my log entries
    arie> (my domain is taken out for obvious sec.  reasons):

Actually your domain name was taken out to make it difficult for
people to help you. Deliberately hiding this information is
counter-productive. It can even be confusing. For example the mangled
zone files you showed mentioned blah.net and another.com. These zones
appear to be fine. And since you mangled the zone files to hide the
real names, who's to say what else you could have mangled when you
edited them? The stuff you posted clearly isn't what you fed your
name servers, so there's no way of knowing for certain what the
problem is.

    arie> Why is the zone accepted in 8.2.2-P5 en rejected in 8.2.3? I
    arie> couldn't find it so quickly in the Docs...

Because the zone file parser in previous versions of BIND was broken.
Read Section 5 of RFC1035 on the format of zone files. Your zone files
appear to be incorrectly formatted - assuming what you showed
resembles what you get your server to load. The software you used
to run tolerated that brokenness.


More information about the bind-users mailing list