HI,

I have a small home network, with my server running dhcp3 (V3.0.1) and bind9 (9.2.4) on ubuntu (5.04). I have managed to set it up to dynamically update dns through dhcp for my XP clients. However, I am at a block on getting the reverse dns updating to work. The message that is get in the syslog is:

Jun 16 21:20:13 rover dhcpd: Added new forward map from Bowser.garbledwords.lan to 192.168.0.10
Jun 16 21:20:13 rover dhcpd: unable to add reverse map from 10.0.168.192.in-addr.arpa. to Bowser.garbledwords.lan: not a zone


The first message show that the forward dns update works and the second shows that the reverse dns update fails saying that the zone that I have set up is "not a zone". But it really seems to be as when I add a static entry to this zone, it works fine. It is the dynamic update part that does not work. Could it be something to do with XP?

(And yes, I know I have no security for this. I was waiting on getting it working first before complicating things.)

I would appreciate any assistance with this problem. Thanks in advance.

Now for the long part - the config files (minus the comments):

dhcpd.conf
----------
ddns-update-style interim;
default-lease-time 600;
max-lease-time 7200;
log-facility local7;

subnet 192.168.0.0 netmask 255.255.255.0 {
update-optimization off;
one-lease-per-client on;
server-name "rover.garbledwords.lan";
range 192.168.0.2 192.168.0.11;
option routers 192.168.0.1;
option domain-name-servers 192.168.0.1;
option netbios-name-servers 192.168.0.1;
option netbios-node-type 8;
ignore client-updates;
option broadcast-address 192.168.0.255;
option domain-name "garbledwords.lan";
}

----------

named.conf
----------
include "/etc/bind/named.conf.options";

zone "." {
type hint;
file "/etc/bind/db.root";
};

zone "localhost" {
type master;
file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};

include "/etc/bind/named.conf.local";

----------

named.conf.options
----------
options {
directory "/var/cache/bind";
auth-nxdomain no; # conform to RFC1035
listen-on { 127.0.0.1; 192.168.0.1; } ;
allow-query { 127.0.0.1; 192.168.0.0/24; } ;
};

----------

named.conf.local
----------
acl garbledwords.lan {
127.0.0.1;
192.168.0.0/24;
};

zone "garbledwords.lan." IN {
type master;
file "/etc/bind/zone.garbledwords.lan";
allow-update { garbledwords.lan; } ;
};

zone "0.168.192.in-addr.arpa." IN {
type master;
file "/etc/bind/zone.0.168.192";
allow-update { garbledwords.lan; } ;
};

----------

zone.0.168.192
----------
$TTL 300
@ IN SOA rover.garbledwords.lan. roy.garbledwords.net. (
1 ; Serial no., based on date
21600 ; Refresh after 6 hours
3600 ; Retry after 1 hour
604800 ; Expire after 7 days
3600 ; Minimum TTL of 1 hour
)
1 IN PTR rover
@ IN NS rover
10 IN PTR bowser
-----------

(A reverse dns lookup on bowser works (nslookup 192.168.0.10)).

-----------

The syslog messages during starting named/
-----------
Jun 16 21:36:52 rover named[30179]: starting BIND 9.2.4 -u bind
Jun 16 21:36:52 rover named[30179]: using 1 CPU
Jun 16 21:36:52 rover named[30179]: loading configuration from '/etc/bind/named.conf'
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface lo, 127.0.0.1#53
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface bridge, 192.168.0.1#53
Jun 16 21:36:52 rover named[30179]: zone 'garbledwords.lan.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: zone '0.168.192.in-addr.arpa.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: command channel listening on 127.0.0.1#953
Jun 16 21:36:52 rover named[30179]: command channel listening on ::1#953
Jun 16 21:36:52 rover named[30179]: zone 0.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 127.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 255.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone garbledwords.lan/IN: loaded serial 7
Jun 16 21:36:52 rover named[30179]: zone localhost/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: running
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 1)
Jun 16 21:36:52 rover named[30179]: starting BIND 9.2.4 -u bind
Jun 16 21:36:52 rover named[30179]: using 1 CPU
Jun 16 21:36:52 rover named[30179]: loading configuration from '/etc/bind/named.conf'
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface lo, 127.0.0.1#53
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface bridge, 192.168.0.1#53
Jun 16 21:36:52 rover named[30179]: zone 'garbledwords.lan.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: zone '0.168.192.in-addr.arpa.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: command channel listening on 127.0.0.1#953
Jun 16 21:36:52 rover named[30179]: command channel listening on ::1#953
Jun 16 21:36:52 rover named[30179]: starting BIND 9.2.4 -u bind
Jun 16 21:36:52 rover named[30179]: using 1 CPU
Jun 16 21:36:52 rover named[30179]: loading configuration from '/etc/bind/named.conf'
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface lo, 127.0.0.1#53
Jun 16 21:36:52 rover named[30179]: listening on IPv4 interface bridge, 192.168.0.1#53
Jun 16 21:36:52 rover named[30179]: zone 'garbledwords.lan.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: zone '0.168.192.in-addr.arpa.' allows updates by IP address, which is insecure
Jun 16 21:36:52 rover named[30179]: command channel listening on 127.0.0.1#953
Jun 16 21:36:52 rover named[30179]: command channel listening on ::1#953
Jun 16 21:36:52 rover named[30179]: zone 0.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 127.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 255.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone garbledwords.lan/IN: loaded serial 7
Jun 16 21:36:52 rover named[30179]: zone localhost/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: running
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 1)
Jun 16 21:36:52 rover named[30179]: zone 0.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 127.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone 255.in-addr.arpa/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: zone garbledwords.lan/IN: loaded serial 7
Jun 16 21:36:52 rover named[30179]: zone localhost/IN: loaded serial 1
Jun 16 21:36:52 rover named[30179]: running
Jun 16 21:36:52 rover named[30179]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 1)

Have you tried adding the "zone" statment for the reverse zone to dhcpd.conf? I have one for each zone (in named.conf) that I want dynamically updated. See: man dhcpd.conf (search for zone)

Other than the missing zone statements in dhcpd.conf, I don't see anything else wrong.

Thank you very much. I thought it would be very simple. I had seen this previously, but when the lookup for the name worked, I must have ignored putting the zones in dhcpd.conf or just thought I had.

Garbledwords

Can any of you specify where you have to add the "zone" statement for the reverse zone in dhcpd.conf file. It wasn't very clear from the context.

You can put the zone statement anywhere in the "global" section (that is, not in a subnet or other specific section).