|
Hopefully you guys can shed some light on this one. We have an AD domain, childdomain.domain.com. The domain
controllers for childdomain.domain.com are Windows 2000 DCs and they are named (on
the Network Identification tab) DC1.domain.com, and DC2.domain.com.
Therefore we have a situation where the DC’s DNS suffix does not match domains
DNS suffix. DC1 and DC2 were setup a number of years ago with this
configuration. We have now introduced a new DC, DC3 into the
domain. DC3 has a FQDN DC3.childdomain.domain.com. We also now have
an Exchange server EX1.childdomain.domain.com. EX1 registered itself in
DNS with its FQDN. As part of initial config it was rebooted, and came
back up with a name EX1.domain.com. We don’t have control of
domain.com (i.e. this part of the puzzle cannot be changed). My questions; How do we fix this? Why did EX1 change its FQDN on reboot (what process caused
this?)? We tried running fixdomainsuffix.vbs (KB257623) on DC2 but it
didn’t work. DC2 doesn’t hold FSMO roles and maybe this is
the problem? Thanks in advance for your help. Tim Foster |
