DNS not updating properly

I have three locations and my users move around between each of the three locations daily.  I have a mix of 2008 and 2012 domain controllers which are also acting as both my DNS servers and DHCP servers for each site.  I'm seeing that as users switch between branches DNS is not updating to reflect their new IP address.  The reason this is a problem is the patch manager I use runs it's scans based off of the hostname and is reporting bad information because when running a ping of the pc's from the patch server it is returning bad IP information from the clients.  What is the best way to resolve this issue.  What I have been doing is running my patch scans manually but before I kick off a scan I checked my address leases on my DHCP server to see what IP address the client should have then I check the A record on the DNS server, if it is incorrect I manually update then flush dns on the patch server then run my scan, obviously this is a pain to have to go through this process every time and if DHCP and DNS were sharing information better this process would be much easier.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Schnell SolutionsSystems Infrastructure EngineerCommented:
Hello Bsjj.

The issues that you have are related to both things:

1. DC replication (Depending your sites configuration, your DCs are configured to replicate every certain amount of time, by default it comes with three hours and could be reduced up to 15 minutes).

2. Records cache (This is what you are correcting cleaning the cache from your patch management server, this is because by default this cache stays in your server and any other hosts for 1 hour).

One manual way to correct it is... first complete a manual AD replication for your DNS servers and then clean the DNS cache like you usually do for your patching server. However, it demands more administrative overhead.

Another solution, which is related to your network design is evaluate if this is possible for your environment to speed up the updates for all of this information. For the issue stated at point '1' you can reduce your replication intervals to 15 minutes for example (You can accomplish this task using the AD Sites and services console), nonetheless, even if AD replication is very efficient, it is something that you should evaluate according your bandwidth and amount of changes made with your AD infrastructure. In order to help the statement '2', you can decrease the TTL (Time to live) used for the dns records for these clients. In this case you will force them to stay for a shorter time been cached.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.