Also, I have a number of stale records in the reverse lookup zone that I really can't explain.The PTR is really annoying but not critical but the fact that we often end up with duplicates or incorrect A records is much more problematic.We have 2 DNS servers and randomly when we move a machine to a different VLAN, the DNS entry never registers the new IP.
If you want more information you may find the following useful: Welcome to Linux Questions.org, a friendly and active Linux Community. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration.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.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…
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.
Note that registered members see fewer ads, and Content Link is completely disabled once you log in. Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
Please visit this page to clear all LQ-related cookies.
I have tried to DIG a few machines and noticed the TTL is 1200 seconds which is 20 minutes, but if you keeping check ing via DIG the time doesn't go down.