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

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?
kstetAsked:
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.

brent_caskeyCommented:
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
kstetAuthor Commented:
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
brent_caskeyCommented:
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

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
Active Directory

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.