We're running a Windows 2008 R2 DC with DNS, AD and DHCP roles on it.
DNS Forward zone is working fine (when a new client is added to the
domain, it registers itself into DNS also).
But the client PTR record in its reverse zone isn't created.
Our network is a class-C segmented network. I manually added a reverse
zone for each subnet as primary reverse ipv4 zone (eg.
26.168.192.in-addr.arpa for 192.168.26.0/24 subnet).
Anyway reverse zones are not populated automatically: i can see only NS
and SOA records.
Zones are integrated in AD, clients are joined to the domain and get IP
address from DHCP.
At the moment, reverse name resolutions don't work (checked using
Forum info: http://www.activedir.org
Problems unsubscribing? Email admin@xxxxxxxxxxxxxxxx
DNS Reverse Zone updates
- 181 Views
- Last Post 02 March 2016
My memory sucks but this sounds like a permissions problem. Check to make sure that the DHCP server is configured to populate the reverse lookup zone, and make sure that the DHCP service has the permissions in AD to do so.
There is some scenario where the client actually does the update, in which case the client machine account needs the permissions. It might be only in the case of non-Windows DHCP, I forget.
I have a vague recollection of having to create a service account with
proper permission on it to get this to work for a couple of quite
locked down forests. I don't think I found it documented anywhere, I
think I just noticed there was a dialog that allowed you to specify
the account to use either on the DHCP or DNS side and I just gave it a
go and it solved all problems.