Yeah that is most likely not going to work. You can try enabling the
DisableStrictNameChecking functionality (KB281308) but there are so many
services something could hit on a DC, I am not sure it would help with all
of them. Even if it does work, I would wonder if it would add some confusion
to apps/processes that you might cause you to encounter some delays.
Obviously you can give it the old college try. However I would do that try
in the lab and get someone above you to sign off on it as being ok. ;o)
joe
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thommes, Michael M.
Sent: Thursday, July 14, 2005 8:53 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] old DCs - alias DNS records enough?
I am getting ready to install new domain controllers (2003/SP1, same as the
old). I want to put up the new DCs with a new names and IPs. We do
AD-integrated DNS but a Unix server is our primary DNS. Because of various
places were the name/IP of a current DC may be buried (like on Exchange
servers with hardcoded GCs or on a non-AD connected TS pointed to the TS
License Server, etc), some in my group are worried and think that we can get
around these problems by having an alias DNS record for the old DC pointing
to the new DC. My gut feeling says this is not going to work.
Thoughts/comments?
Mike Thommes
List info : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
