DNS/DHCP Auto-Update "not a zone"

[Kevin Darcy]

Jan Peuker wrote:

> At first, I will excuse myself for not respecting the rules of formatting
> postings to this group.
> My Bind-Version is 8.2.4-RE2, my SOA-records(it thought they were the same)
> are in the appended Files.
> But now, my Bind-History:
> I made changes to my config-files, added real names("hauptserver") and @'s,
> reset the original files for localhost from the distribution and copied all
> SOA-Headers.
> Then, I got the message "destination address required." in my warn-log for
> dhcp, what I supposed to be a DNS Error again.
> A nslookup to hauptserver.netzwerk resolved
>  Server:hauptserver.netzwerk
>  Address: 192.168.100.101
>
>  *** hauptserver.netzwerk can't find hauptserver.netzwerk: Server failed.
>
> This reminds me of Windows-Networks, but I think, this time it's my fault.
> I found out, that recusively queries are being processed (e.g. host
> 192.168.100.101 returned hauptserver.netzerk).
> So I added another test-entry in my files and IT WORKED. But do you now
> while my old file didn't?
>
> follow up: named.conf, netzwerk.zone, test.zone after original message
>
> ----- Original Message -----
> From: <Mark_Andrews at isc.org>
> To: <B.Weeber at viastore.de>
> Cc: "BIND Liste (E-Mail)" <bind-users at isc.org>
> Sent: Wednesday, April 17, 2002 10:56 PM
> Subject: Re: DNS/DHCP Auto-Update "not a zone"
>
> >
> > >
> > > This is rather a DHCP question.
> > > Your dhcp.conf file is missing the ddns-domainname statement where your
> have
> > > to enter your domainname also.
> >
> > I doubt that that is the problem in this case as the log entry has
> > the correct domainname.
> >
> > I suspect the problem is that the "localhost" is the nameserver.
> > Also MX records should never point to localhost.  Replace these
> > localhosts with the real name of the nameserver along with the
> > MNAME field in the SOA.
> >
> > Verify that the nameserver starts cleanly.  Also in future
> > post your zone files exactly as they are.  "blah" is not useful
> > when you are looking for syntax errors.  Also the full BIND
> > version would be useful.
> >
> > Mark
> >
>
> ----------named.conf
> acl internal{ 127.0.0.1;192.168.100/24; 192.168.0/24; };
>
> options {
>  directory "/var/named";
>  listen-on port 53 {
>   127.0.0.1;
>   192.168.100.101;
>  };
>  query-source address * port 53;
>  allow-query { internal; };
>  cleaning-interval 120;
>  statistics-interval 0;
>  notify no;
>  interface-interval 0;
> };
>
> logging {
>  category default { null; };
> };
>
> # THIS HANGS!
> zone "netzwerk" in {
>  type master;
>  file "netzwerk.zone";
>  allow-update { internal; };
>  notify no;
> }

You need a semicolon (";") here.

> zone "localhost" in {
>  type master;
>  file "localhost.zone";
> };
>
> # THIS IS WORKING!
> zone "test" in {
>  type master;
>  file "test.zone";
>  allow-update { internal; };
>  notify no;
> }

You need a semicolon here also. Apparently two syntax errors sometimes gets
the parser further than a single one does (i.e. more errors actually yield
better results, paradoxically).

You should make it a habit to look more closely at your logs. These errors
should have been reported in significant detail.


- Kevin