Incorrect DNS A records appearing on Domain Controllers

I have a Server 2008R2 machine running a couple of SharePoint sites via IIS. Each site has it's own IP, each IP is assigned to a separate physical NIC on the machine. Each site has it's own A record in DNS.

The problem is, every day or two, a second A record appears for one of the site's IPs, pointing it to the wrong FQDN.


A Records exist for: - -

Every day or two, a second A record appears for: -

This new, erroneous A record does not REPLACE the original record for, but rather, it co-exists with it, causing resolution issues.

I don't think I want to disable dynamic DNS on the Domain Controllers, but I need this second A record to stop appearing!

Any ideas?
Who is Participating?
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.

I believe if you go to the connections properties, in advanced, in the DNS tap, select Append these DNS suffixes (and enter yours) and select Use this Connections DNS suffix in DNS registration.
MikeR428Author Commented:
But the DNS suffix isn't the issue here.

The issue is, two A records are appearing for the same name, but for two different IPs.

I create the A record that points to

But the machine itself is registering with DNS, with the same name, but pointed to instead of, creating multiple A records for the same domain name, with different IPs.

The DNS suffix for both domain names is, the issue is merely the IP address listed in the A record.

I think I'm missing something here...
On the NIC in dns properties uncheck register DNS record.  The NIC won't register its IP with DNS then

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
Darius GhassemCommented:
The only way is to uncheck register this interface with DNS
MikeR428Author Commented:
While this solution does not deal with the root cause of the error, it is an exceptional workaround with the exact same desired results.
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

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.