DNS/DHCP Auto-Update "not a zone"

Burkhard Weeber B.Weeber at viastore.de
Wed Apr 17 16:13:23 UTC 2002


This is rather a DHCP question.
Your dhcp.conf file is missing the ddns-domainname statement where your have
to enter your domainname also.

Burkhard Weeber
viastore systems GmbH
P/O Box 300668
D-70446 Stuttgart
Tel: +49-711-9818-0
Email: B.Weeber at viastore.de

Disclaimer:
The opinions expressed herein are my personal points of view and do not
represent those of my employer.

Windows95: <win-doz-nin-te-fiv> n.
32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit
operating system originally coded for a 4 bit microprocessor, written by
a 2 bit company, that can't stand 1 bit of competition.



> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
> Behalf Of Jan Peuker
> Sent: Wednesday, April 17, 2002 4:35 PM
> To: bind-users at isc.org
> Subject: DNS/DHCP Auto-Update "not a zone"
>
>
>
> Hi all,
>
> this is a newbie question. I set up a DNS(BIND8) and a
> DHCP(3.0rc12) and a
> Suse7.3-Linux(also Samba as PDC installed) both are running
> beautiful. But
> if I try to automatically update the DNS with (netbios)-Names of the
> DHCP-Clients I get this Error Message:
> dhcpd: if IN A toshiba.netzwerk rrset doesn't exost add 300 IN A
> toshiba.netzwerk 192.168.100.114: not a zone.
> So, this seems to be a Error Message of the DNS instead of
> the DHCP. But
> what is wrong?
> My files are are the bottom, thank you very much
>
> Jan Peuker
>
>
> -----------dhcpd.conf
> default-lease-time 600;
> max-lease-time 14400;
>
> option domain-name "netzwerk";
> option domain-name-servers 192.168.100.101;
> option broadcast-address 192.168.100.255;
> option routers 192.168.100.101;
> option subnet-mask 255.255.255.0;
>
> ddns-update-style ad-hoc;
>
> subnet 192.168.100.0 netmask 255.255.255.0
>  {
>   range 192.168.100.102 192.168.100.199;
>   option subnet-mask 255.255.255.0;
>   option broadcast-address 192.168.100.255;
>   option domain-name-servers 192.168.100.101;
>   option routers 192.168.100.101;
>   option ntp-servers 192.168.100.101;
>   option netbios-name-servers 192.168.100.101;
>   option netbios-dd-server 192.168.100.101;
>   option netbios-node-type 8;
>  }
>
>
> -----------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;
> };
>
> logging {
>  category default { null; };
> };
>
> zone "netzwerk" in {
>  type master;
>  file "netzwerk.zone";
>  allow-update { localhost; };
> }
>
> zone "localhost" in {
>  type master;
>  file "localhost.zone";
> };
>
> zone "0.0.127.in-addr.arpa" in {
>  type master;
>  file "127.0.0.zone";
> };
>
> zone "local" in {
>  type master;
>  file "local.zone";
> };
>
>
> zone "100.168.192.in-addr.arpa" in {
>  type master;
>  file "192.168.100.zone";
>  allow-update { localhost; };
> };
>
> zone "." in {
>  type hint;
>  file "root.hint";
> };
>
> -----------netzwerk.zone
> $TTL 2D
> netzwerk. IN SOA  localhost. webmaster.netzwerk. (
>   blah )  ; minimum
>
>   IN NS  localhost.
>   IN MX  10 localhost.
>
> hauptserver IN A  192.168.100.101
>
>
> -----------localhost.zone
> $TTL 2D
> @  IN SOA @   root (
> blah )  ; minimum
>
>   IN NS  @
>   IN A  127.0.0.1
> localhost. IN A  127.0.0.1
> localhost IN A  192.168.100.101
> hauptserver. IN A  127.0.0.1
> hauptserver. IN A  192.168.100.101
>
>
> -----------192.168.100.zone
> $TTL 2D
> 100.168.192.in-addr.arpa.  IN SOA  test.local.  root.localhost. (
>   blah )  ; minimum
>
>   IN NS  test.local.
>
> 1  IN PTR  test.local.
> 101  IN PTR  hauptserver.netzwerk.
>
>
>



More information about the bind-users mailing list