Dhcp clients not updating dns

Response time of the DNS server is critical to the speed and performance of relying services.

These two blogs have the timeout information and DNS client behavior explained in detail (DNS…

Click Here to receive this Complete Guide absolutely free.

If you find that you can not resolve IP’s back to a name on your network check your DNS REVERSE LOOKUP ZONE.

If there are missing entries, you likely have your DHCP missing one of two settings: This is required if you have DHCP installed on a Domain Controller.

The DHCP server is setup to always update both A and PTR record.

The problem is that the PTR aren't actually updated and, sometimes, the A record isn't either.

We have a network with a segment for client machines that uses a couple of Windows 2008 R2 servers for DNS and DHCP (all AD-integrated).

Clients are mostly Windows 7 machines with a few XP and Vista.

The way we solve this is by manually deleting the offending records and issue "ipconfig /registerdns" on the client.

No error is logged in the event viewer of either the client and the server.

I've looked at it, my co-worker has looked at it and neither of us could find anything wrong with the system: we just don't understand why the records aren't properly updated.

If you are working with, well almost anything network intensive these days, like Antivirus or management tools, your Reverse DNS (r DNS) lookups need to be in good shape.

This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.

Tags: , ,