Link to home
Start Free TrialLog in
Avatar of MikeR428
MikeR428Flag for United States of America

asked on

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.

Example:

A Records exist for:

Machine1.domain.com - 10.1.4.1
Machine2.domain.com - 10.1.4.2

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

Machine2.domain.com - 10.1.4.1

This new, erroneous A record does not REPLACE the original record for Machine2.domain.com, 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?
Avatar of sysreq2000
sysreq2000

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.
Avatar of MikeR428

ASKER

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 Machine2.domain.com to 10.1.4.2

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

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

I think I'm missing something here...
ASKER CERTIFIED SOLUTION
Avatar of Vinchenzo-the-Second
Vinchenzo-the-Second
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Darius Ghassem
The only way is to uncheck register this interface with DNS
While this solution does not deal with the root cause of the error, it is an exceptional workaround with the exact same desired results.