DNS/DHCP Auto-Update "not a zone"

[Jan Peuker]

My old named.conf contained the option "categeory default {  null; }".
Now I changed to your configuration and got 1 error messages to my errorlog:
"unknow facility local()","syntax error near "debug 1", "unknown channel
syslog_debug"(!). This seemd to be your whole context, but after deleting
the "syslog_debug" and just leaving "category default { default_syslog;}" it
runs(hopefully it won't log too much...)

Thanks a lot/vielen Dank

Jan
----- Original Message -----
From: "Holger Honert" <holger.honert at signal.de>
To: <bind-users at isc.org>
Sent: Friday, April 19, 2002 8:37 AM
Subject: Re: DNS/DHCP Auto-Update "not a zone"


> Hello Jan,
>
> maybe I have a solution to you. My named.conf file for logging in syslog
> daemon
>
> logging {
>         channel syslog_debug {          // this channel will send debugs
or
>                 syslog local0;          // or worse to syslog (local0
> facility)
>                 severity debug 1;
>         };
>
>         category default {
>                 syslog_debug;
>         };
> };
>
> in syslog.conf :
>
> local0.debug            /var/log/named.log
>
> you can choose any other location the log file is located, respectively
> the name for
> the log file.
> I am running BIND on a AIX 4.3.3 box, so this statements may be
> different on other UNIX
> systems
>
> regards
>
> holger
>
>
>
> Jan Peuker wrote:
>
> >
> >Damn. I looked to my logs but it was not logged. Named started
succesfully
> >without any warning or message in any log. But I excuse myself for this
> >stupid error, even if I don't really know how it runs. Is there any
ability
> >to set a seperate log-file and a much higher loglevel (e.g. i run samba
in
> >loglevel2).
> >Thanks a lot,
> >
> >Jan
> >
> >----- Original Message -----
> >From: "Kevin Darcy" <kcd at daimlerchrysler.com>
> >To: <bind-users at isc.org>
> >Sent: Thursday, April 18, 2002 11:57 PM
> >Subject: Re: DNS/DHCP Auto-Update "not a zone"
> >
> >
> >>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
> >>
> >>
> >
> >
>
>
>
>