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)
Main Topics
Browse All Topics





by: brent_caskeyPosted on 2008-10-30 at 22:50:24ID: 22847845
Hello kstet,
om/kb/2722 94
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.c
Regards,
brent_caskey