DNS Issues in server 2003 multi domain environment.
i have 5 offices, each own child domain, , parent domain keep namespace. 1 of children had ad domain controller issues , domain controller replaced. when domain controllers running, fine. can reboot either domain controller , still, fine. then, office these in have had several power events (post hurricane sandy recovery), requiring power down equipment. when domain controllers come up, takes 15+ minutes login screen. once login screen, if trying rdp domain controller, message domain doesn't exist! if can physically log server console, resumes normal. member servers can authenticate , can have end users log in again.
well, have shut down next 4 weekends in row, , i'm afraid isn't going come right. don't want 1 can things running again, other coast!
i suspect dns issue. can tell, forward zones fine. reverse zone network not. network, have 20.172.in-addr.arpa, , 20.172.in-addr.arpa/1. under 20.172.in-addr.arpa, see ns records , soa. under 20.172.in-addr.arpa/1, have prt records machines matching 172.20.1.x. i do not have other folders 20.172.in-addr.arpa/2, 20.172.in-addr.arpa/3, etc prt records pc's , other machines.
all zones ad integrated, not have zone transfers configured.
how fix these? delete zones, recreate on domain controller in office's domain? need remove reverse zone, wait replicate (how long) create reverse zone? assuming full replication, take hours. how of affect have on production traffic?
this posting provided "as is" no warranties or guarantees , , confers no rights.
get active directory user last logon create active directory test domain similar production one management of test accounts in active directory production domain - part i management of test accounts in active directory production domain - part ii management of test accounts in active directory production domain - part iii reset active directory user password
Windows Server > Directory Services
Comments
Post a Comment