Active Directory DNS Dilemma
i have remote office have child domain , 2 dcs domain. have dc in remote office our domain tree. 3 dcs run ad integrated dns. our domain computers in remote office on 1 vlan , have same dns servers assigned them whether belong child domain or root domain. dilemma having don't control dhcp server , our computers getting assigned dns server not ours(not child dcs or root dc). can still reach our dns servers via servers since know our 2 domains dns servers located in central site , takes 15 hops remote site reach it. because of this, have been having slow logons since have been deploying gpos logon issues no logon servers found.
the best solution create 2 vlans computers joined child domain , child domain dcs in 1 , other computers part of our root domain dc root in site on another. not viable solution @ point in time , can change dns servers 1 vlan members of. question is, should dns servers set to? should make primary dns server root dc in remote site or should primary dns server set child dc in site? since have ad integrate dns our child , parent know each other not sure issues experience if 1 of dc's set primary whole vlan have mixed of clients belong either child or root domain. thank help.
hi,
i suggest creating seperate vlan , avoid problems in future if in case remote site expanding.. dns crucial network , has defined properly.else, common you'll face slow logons issue. having mixed dns entries in child or root domain not resolve problem... but try giving root domain dc primary dns , child domain dc secondary dns.
regards, mohan r sr. administrator - server support
Windows Server > Directory Services
Comments
Post a Comment