Solved

Multi-home Windows 2003 AD Server - Issue with DNS Host A record disappearing

Posted on 2008-10-30
5
775 Views
Last Modified: 2012-05-05
I have a Windows 2003 server with 2 NICs.  It is using both NICs - they are on different subnets.
For some reason - the A (host) record for the one NIC will register in DNS and stay there.  The other (from the other NIC) will not.  I can even manually add it - but in a short period of time - approximately 10 minutes - the A record I create will be gone.  What is making this A record I add - disappear?
0
Comment
Question by:kstet
  • 2
5 Comments
 
LVL 13

Expert Comment

by:brent_caskey
Comment Utility
Hello kstet,

I dont think that you will want both IP addresses to register in DNS. This usually causes AD replication issues on the domain controller. When there are 2 NICs on the domain controller, dns name resolution lookup returns requests in a round robin fashion. If both addresses are registered in DNS and you have clients in subnet A trying to find this domain controller, the dns server may return the domain controllers subnet B address. The same would go for other domain controller trying to contact this domain controller while they are trying to replicate.

Here is a reference article for more information: http://support.microsoft.com/kb/272294

Regards,

brent_caskey
0
 

Author Comment

by:kstet
Comment Utility
Hi Brent.  Thanks for the reply.
I can see how having it multihomed is an issue - but there are reasons I need to keep it this way for now.
The issue really is - why is the A Host record for the subnet B being deleted from DNS?
I'm adding it - but it is disappearing after about 10 to 15 minutes or so.
What is actually deleting it - and how can I make that A Host record stay in DNS?

Maybe coming about this a different way - what if I left it out of DNS.
But in the other Domain controller - I put something in the hosts file, etc. - so it could find it's partner domain controller.  
What entry would I need to put in what file (hosts, something else) so that one comain controller could see another (without using DNS)?    (it used to be LMHOSTS - or HOSTS - when using WINS)
0
 
LVL 13

Accepted Solution

by:
brent_caskey earned 500 total points
Comment Utility
On the nic in subnet B, in the advanced properties, do you have it set to register the dns connection? If not, it may be removing the record itself.

You can set up an A record manually and deny the servername$ account the delete permissions.
0

Featured Post

Backup Your Microsoft Windows Server®

Backup all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Join & Write a Comment

Introduction You may have a need to setup a group of users to allow local administrative access on workstations.  In a domain environment this can easily be achieved with Restricted Groups and Group Policies. This article will demonstrate how to…
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now