Dns reverse lookup zone not updating
The two main zones that are used in Active Directory (or Windows Server 2003 and up) are the primary and Active Directory-integrated zones.You could say that an Active Directory-integrated zone is an improved version a primary DNS zone because it can use multi-master replication to other DNS servers in the domain and use the security features of Active Directory.In Active Directory there are a number of different zone types.We’ll list them all below: The primary zone is the only zone that can be edited since it is the original data source for all domains in the zone.Fix is to verify that all your DHCP servers are members of the "DNSUpdate Proxy" default security group in the AD Users container.Is that rule true for Win2K Mixed-mode domains with child domains running 2003 DCs and 2003 DHCP servers?DNS is an important prerequisite of Active Directory.
At any rate, I had the same problem as lordofthepants and, via the KB, I ran it down to to this DNSUpdate Proxy issue.
This is the second article in our series about Active Directory.
In this article, we’ll discuss DNS and Active Directory integration and give you some best practices for your DNS server administration.
Originally posted by Arbelac: Do you have scavenging turned on for the zone and for the server?
If you have more than one server, all of them need to be enabled with the same settings, otherwise old data will be replicated back. Assuming you're also running MS DHCP: In the DNS tab of the scope properties, have you enabled "Enable updates for DNS clients that do not support dynamic update"?
Search for dns reverse lookup zone not updating:
We can't move to native-mode anything due to NT4 BDCs (they were Exchange 5.5 servers).