DHCP server and Windows 2003 DNS

[Glenn Satchell]

The default value for ddns-rev-domainname, "in-addr.arpa" is
sufficient, so remove this entry from your definitions. The fact that
it is working for one subnet is probably a fluke :)

 man dhcpd.conf
 ...
     The ddns-rev-domainname statement

       ddns-rev-domainname name; The name parameter should be the
       domain name that will be appended to the client's reversed
       IP address to produce a name for use in the  client's  PTR
       record.    By  default,  this  is "in-addr.arpa.", but the
       default can be overridden here.

       The reversed IP address  to  which  this  domain  name  is
       appended is always the IP address of the client, in dotted
       quad notation, reversed - for example, if the  IP  address
       assigned  to  the client is 10.17.92.74, then the reversed
       IP address is 74.92.17.10.   So  a  client  with  that  IP
       address  would,  by  default,  be  given  a  PTR record of
       10.17.92.74.in-addr.arpa.

regards,
-glenn

>To: dhcp-server at isc.org
>From: Nolan Garrett <nolan at massivegeek.com>
>Subject: DHCP server and Windows 2003 DNS
>Date: Wed, 02 Aug 2006 17:41:58 -0700
>
>Hello!  I am struggling with an issue on my local network.  I am using
>the DHCP server on a Linux box to assign IP addresses.  I have two
>subnets - on one subnet I am using W2K3 DNS, on the other I am using
>BIND, running on the same box as DHCP.  I've configured DHCP to update
>DNS.  It seems to work fine for BIND, but for the W2K3 DNS the IP
>addresses that are being added to the reverse map are in the form of
>192.168.192.168.0.1 - it's prepending 192.168. to the actual IP address.
> Forward mapping is functioning appropriately.
>I've Googled this problem extensively and haven't found anything.  Here
>is my dhcpd.conf:
>
>allow client-updates;
>allow unknown-clients;
>authoritative;
>ddns-updates on;
>ddns-domainname "massivegeek.local";
>ddns-update-style interim;
>include "/etc/rndc.key";
>
># Trusted Network
>subnet 192.168.0.0 netmask 255.255.255.0 {
>        ddns-rev-domainname "0.168.192.in-addr.arpa";
>        option domain-name "massivegeek.local";
>        option domain-name-servers 192.168.0.3, 192.168.0.1;
>        option broadcast-address 192.168.0.255;
>        option routers 192.168.0.1;
>        range 192.168.0.100 192.168.0.254;
>        option smtp-server 192.168.0.1;
>
>}
># Untrusted Network
>subnet 192.168.1.0 netmask 255.255.255.0 {
>        ddns-rev-domainname "1.168.192.in-addr.arpa";
>        option domain-name "massivegeek.local";
>        option broadcast-address 192.168.1.255;
>        option domain-name-servers 192.168.1.1;
>        option routers 192.168.1.1;
>        range 192.168.1.50 192.168.1.254;
>        option netbios-name-servers 192.168.1.1;
>        option smtp-server 192.168.1.1;
>        }
>zone massivegeek.local. {
>        primary 192.168.0.3;
>        }
>zone 1.168.192.in-addr.arpa. {
>        primary 192.168.1.1;
>        }
>zone 0.168.192.in-addr.arpa. {
>        primary 192.168.0.3;
>        }
>
>
>I appreciate any insight you all can give!
>
>Nolan
>
>
>