Greetings, I have set up a test NW6.5 SP3 server with DNS/DHCP and created a test.com domain, I assigned 192.168.1.98/24 to the server, and created an IN-ADDR-ARPA zone for 192.168.1.0. I then set up DHCP for the 192.168.1.0 subnet, and this worked. I then configured Dynamic DNS on the 1.0 subnet.

At first the Dynamic DNS was not working, and to get it working I had to create an IN-ADDR-ARPA zone for 192.168.0.0. Then DDNS would bring the objects into the test.com zone properly, however the IP address and PTR record appeared under the 192.168 IN-ADDR-ARPA zone, not the respective 192.168.1.0 zone.

On the workstation I used nsloopup, and I would get an error "Can't find server name for 192.168.1.98" however I could ping the DNS server's name, and get a reply. In order to fix this I created an IN-ADDR-ARPA zone specifically for the DNS server's IP address 192.168.1.98. DNS did work with only the 192.168.1.0 zone, however the workstation did not see the default server properly when using nslookup until I created the 192.168.1.98 zone.

I then assigned a secondary IP address to the server (192.168.2.1/24), and created the Subnet 2.0 in DHCP. In this subnet I wanted to be able to assign addresses manually. I created the IN-ADDR-ARPA zone for 192.168.2.0,and created a manual assignment in the 2.0 subnet range for a PC. I tested the PC and the PC picked up the assignment, the Resource record was placed in the test.com zone, however IP address, and PTR record were placed under the 192.168 zone and not the 192.168.2.0 zone.

Questions:
Why do I have to create an IN-ADDR-ARPA zone specifically for the server's IP address, in order for the workstation to identify the default server in NSLookup? Looks like 192.168.1.98(98.1.168.192 IN-ADDR-ARPA)

Why do I have to create the 192.168.0.0. zone (looks like 192.168(168.192 IN-ADDR-ARPA) in order to get Dynamic DNS to work, when I am using class C subnets, and have the corresponding zones configured for those subnets?

And finally, why does the Dynamic DNS place the IP addresses/PTR records of the acquired workstations into the 192.168.0.0 zone and not the corresponding zone for the two subnets 192.168.1.0, and 192.168.2.0 respectively? I must be missing something, or is this working as designed?

It is also possible I need to FDISK and start over, but thought I would ask these just in case there were legitimate reasons for the above.

Another annoyance is having to shut down, and restart DHCPSRVR each time I create a manual assignment.

Thanks for taking the time to read this, and any insight would be much appreciated.

Darol