Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 375
  • Last Modified:

RDNS Entries missing for zone

My DC's are also DNS servers and run Server 2008 R2. I recently noticed that I couldn't resolve IP addresses to host names for most of the hosts on my network. I checked my Reverse Lookup Zone for this subnet and found that only a small fraction of the hosts were listed. In other words, dozens of hosts can't be resolved in reverse because they are missing from the reverse lookup zone.

How can I fix this so that the reverse zone will be updated regularly with the correct information as hosts get new IP's via DHCP?

Thanks.
0
Stuart_Page
Asked:
Stuart_Page
  • 2
  • 2
1 Solution
 
Gerald26Commented:
If the  DHCP server is running on Windows Server you can do it.
The server must have the good DNS IP, pointing to integrated AD DNS zone server. Then you can check DHCP Server properties, DNS tab and choose if you either want to register devices that request a DNS registration (windows clients) or all devices, even those who dont need a RDNS entry (nt4, switchs, other network devices)

This will autopopulate DNS and RDNS zones
0
 
Stuart_PageAuthor Commented:
Thanks for the help. This worked for the majority of hosts, however I am still having a few hosts that still won't show up in the Reverse Lookup Zone, even after a reboot.

Thanks.
0
 
Gerald26Commented:
What kind of devices are these hosts ? are they wire connected or using wifi?

If they are windows 2000/xp/2003/2008/vista/seven computers, try ipconfig/registerdns and check if ptr if updated manually
You can check the same step with a static IP since ipconfig /registerdns will bypass DHCP, but the host must have a valid AD dns server in its TCPIP properties
DNS eventlog might also give you some clues of what is happening
Double check your server properties.

Give us all details about the steps, what works and what doesnt.

Regards
0
 
Stuart_PageAuthor Commented:
Gerald was the most helpful in this. Turns out my DNS zones weren't replicating across DC's.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now