Cache Posted May 27, 2014 Posted May 27, 2014 Hi All I'm getting ready to demote the final DC that was here when I started which I've been putting off for quite a while now. Checking everything and getting ready to do it, I've spotted the delegated _msdcs under the domain.local DNS zone however in the delegation it only has this original DC listed. Couple of questions which I can't seem to find a straight answer too: Is it normal for it just to list a Single DC? Do I need to add my other 2 DC's to the delegation before demoting? Do I need to do anything else to look after this delegated zone? Any advice much appreciated.
snagrat Posted May 27, 2014 Posted May 27, 2014 Assuming you have no DNS errors in eventvwr then I usually leave it alone. 1
jinnantonnixx Posted May 27, 2014 Posted May 27, 2014 (edited) You should be OK just letting DNS sort itself out. I've seen pickles where we have strange routing over multiple sites. Have you got a single site (under AD sites and services)? It's been a while since I got deep into DNS, but I think it works like this: Client pings each of the DCs it finds in _msdcs/dc/_tcp If it gets a reply it will look up in (by IP) under AD's sites and services and find the site of DC, and hence the site it belongs to It will then bind to that DC (under _sites//_tcp) and this will be its domain controller for that session. Edited May 27, 2014 by jinnantonnixx 1
Cache Posted May 27, 2014 Author Posted May 27, 2014 I haven't done the demotion yet, I'm just busy checking things ready to demote it tomorrow. Just trying to avoid any potential problems that may crop up. We are a single site AD all sat under the Default-First-Site.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now