We have 2 DHCP/DNS servers (Primary/Secondary) to manage our Terminals on a
private network. Our terminals use DHCP to obtain addressing an in turn use
dynamic updates to update the DNS server. All is well!
A new network was created and added to our environment, but a new Reverse
Lookup zone was not created (forgot!) on the DNS server to allow the DHCP
Server to dynamicaly update its records. The new terminals were able to add
an "A" record in he froward lookup zone, but since there was no reverse, we
cannot do name resolution properly.
We have since created a new reverse lookup and any new terminals coming in
are now being added properly to both the forward and reverse lookups and name
resolution is functioning properly.
Is there a way to force the terminals that only have a forward lookup record
entry to automatically update themselves in the reverse lookup zone?
We tried to use the Update Associated Pointer (PTR) record option under the
properties of an A record host but it does not seem to work.
Any suggestions? We do not necesarilly want to have to add each entry
manually and are looking for a way to force the Reverse zones to repopulate.