Hi All,
I have a situation where we have 20 domain controllers spread across several sites and domains with inconsistently set static conditional DNS forwarders on each machine.
To resolve this issue and maintain the name resolution that these forwarders are providing during production hours I'm going to configure all the forwarders as AD Integrated.
My question is - What is the behavior when a DNS conditional forwarder exists both statically on the DC and in AD Integrated? Which takes precedence, are there errors logged?
I was hoping to remove the statically assigned forwarders after introducing the AD integrated ones so that is is zero name resolution downtime but if the overlap will cause issues I'll have to remove all the statics first quickly, then deploy the AD integrated values out of hours.
I have a situation where we have 20 domain controllers spread across several sites and domains with inconsistently set static conditional DNS forwarders on each machine.
To resolve this issue and maintain the name resolution that these forwarders are providing during production hours I'm going to configure all the forwarders as AD Integrated.
My question is - What is the behavior when a DNS conditional forwarder exists both statically on the DC and in AD Integrated? Which takes precedence, are there errors logged?
I was hoping to remove the statically assigned forwarders after introducing the AD integrated ones so that is is zero name resolution downtime but if the overlap will cause issues I'll have to remove all the statics first quickly, then deploy the AD integrated values out of hours.
Thanks for the input.
Ashley