DNS/DHCP update problem

[organman]

I've changed the subnetmask from 255.255.255.0 to 255.255.254.0 on the 172.16.2.0 network.

The idea is to move my workstations from 172.16.2.0 net to the 172.16.3.0 net.

They all get their ip address fom dhcp server at 172.16.2.2.

So I stopped dhcpsrvr and changed the netmask on the server, then ran reinitialize system.Then I removed the subnet objects.
Recreated new subnet objects and a new range for 172.16.3.1 to 172.16.3.254.
Started dhcpsrvr.

When rebooting a workstation it will get a new ip address, 172.16.3.1.

However my dns server wich is running on the same box as dhcp will not be updated with the new ip address for the workstation.

The "DNS Update Option" is set to Always Update.

When looking on the workstation object in C1 it has the new ip address.

I've tried unloading and then load named, no sucess.
I've rebooted the server that runs both named and dhcpsrvr, no sucess.

What could be the problem here ?

 

[marvhuffaker]

Turn on debugging on the NAMED.NLM service. This will allow you to see what is happening on the service.

LOAD NAMED -DL 3

look here for further reference:

http://www.novell.com/documentation...umentation/lg/nw65/dhcp_enu/data/fb14532.html

Marvin Huffaker, MCNE

http://www.redjuju.com

See me speak at GWAVACON Jan 21-23 in Dallas.

http://www.redjuju.com/company/events.htm

 

[organman]

Problem solved.
I got the message "Cannot add FQDN: workstation namne and ip address to DNS server" on the server console.
In the DNS server screen on the console I got the message "Can not find reverse zone".

This made me think that there was some problem with the IN-ADDR.ARPA zone.

I had done a change of the netmask for 172.16.2.0 network to 255.255.254.0 earlier.
(Wich means that 172.16.2.0 network now includes 172.16.2.1 to 172.16.3.254)

So I created a new IN-ADDR.ARPA zone for 172.16.3 and then restarted named.

Now the workstations will appear correct in DNS and no error messages on the server console.