Migrating from statically defined conditional DNS forwarders to Ad integrated DNS forwarders
have situation have 20 domain controllers spread across several sites , domains inconsistently set static conditional dns forwarders on each machine.
resolve issue , maintain name resolution these forwarders providing during production hours i'm going configure forwarders ad integrated.
question - behavior when dns conditional forwarder exists both statically on dc , in ad integrated? takes precedence, there errors logged?
hoping remove statically assigned forwarders after introducing ad integrated ones is 0 name resolution downtime if overlap cause issues i'll have remove statics first quickly, deploy ad integrated values out of hours.
thanks input.
ashley
yes; conflicts still apply adi conditional forwarders. dns treated zone.assume have conditional forwarder contoso.com not able create zone called "contoso.com". hope make sense.
have look.
regards
biswajit biswas
my blogs|technetwiki ninja
best regards biswajit biswas disclaimer: posting provided "as is" no warranties or guarantees , , confers no rights. mcp 2003,mcsa 2003, mcsa:m 2003, ccna, mcts, enterprise admin
Windows Server > Directory Services
Comments
Post a Comment