Windows dns reverse lookup zone not updating

Rated 4.35/5 based on 688 customer reviews

Reverse lookup zones and PTR resource records are not necessary for Active Directory to work, but you need them if you want clients to be able to resolve FQDNs from IP addresses.Also, PTR resource records are commonly used by some applications to verify the identities of clients.

Then check the Security tab on the Reverse Zone and make sure that group is authorized to create all child objects (DNS records) 2) If your statically-configured hosts are not updating the reverse zone, make sure their NICs are configured to register their IP in DNS (Windows hosts are enabled for this by default).

For example, if you have only one class C network identifier (even if you have subnetted your network), it is simplest to organize your reverse lookup zones along class C boundaries.

You can add the reverse lookup zone and all the PTR resource records on an existing DNS server on your network.

The spiceworks logs give me an error of: (finder_ar) **Ldap AD**: real domain from ping returns nil **Ldap AD**: failed looking for full domain: nslookup of short domain returned: Server: ctcdc01.com Address: 10.1.1.10 Also i'm thinking that the network might think we have two DNS servers (ipconfig also see's 10.1.1.30 as a DNS server) but that server used to be the old DNS at the old location but now is just the utility box that we push WSUS from.

Sorry for the wall of text but didn't want to leave anything out!

Leave a Reply