Windows DNS server - force A record to update PTR record

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.

My Question:
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.

Thank you

Peter Cumming wrote:
> 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.
>
> My Question:
> 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.
Update PTR only works if the PTR exists.

> 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.

If DHCP is registering in DNS for the clients, and the clients are XP, use
repair this connection, if the client registers itself use ipconfig
/registerdns, if the client doesn't support DDNS, DHCP is registering the
client, so use ipconfig /release & ipconfig /renew

Unless you have an application that requires a reverse lookup IP to name
reverse lookups are not really required for normal connectivity.



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================