Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a firewall appliance that uses DNS records of PCs and user authentication from LDAP. (Windows environment). The PCs in the environment are displaying old DNS records and not updating. This in turn is affecting the firewall (due to multiple computers having the same DNS record). It isnt happening to all workstations. Majority are updating but some just wont. Any ideas? DHCP is providing the addresses no problems but from there the new records dont seem to be getting to DNS.

Thanks

share|improve this question

1 Answer 1

up vote 0 down vote accepted

Check the permissions on the DNS entry directory objects in the DomainDNSZones/ForestDNSZones container.

I've seen situations where the permissions don't allow the workstation to update its own address due to permissions issues, specifically a DHCP server creating DNS entries on behalf of clients that have restrictive permissions (but static entries created by a user would do the same).

Are the offending entries static? If they aren't.. do you have scavenging enabled?

And, stating the obvious, but: make sure the "Register this connection's address in DNS" box is checked on the NIC (IPv4 -> Advanced).

share|improve this answer
    
Where are the permissions applied to this container. I see the container in DNS but no security options. Thanks for the quick post –  JohnyV May 5 '11 at 4:29
    
You'll actually want to look at the permissions on the individual entries, as that's any permission problems would reside. ADSIEdit is probably the best way to get a look at the real structure of the AD-integrated DNS and the security settings for the objects. –  Shane Madden May 5 '11 at 4:34
    
ok cheers, scavenging is enabled. Entried are not static. All DHCP –  JohnyV May 5 '11 at 4:38
    
I found that there was a broken sid in the records that were not updating. When I deleted the record and performed a registerdns on the client the broken sid was replaced by the computername$ which had full control. This must have been the permission that was the issue. –  JohnyV May 5 '11 at 23:43

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.