The network I currently manage will shortly be expanding to cover two sites, and due to the organisation of the company, I have already determined that a site-to-site hardware VPN will be implemented to link the two sites. The WAN link between the two will be between 20-100mb so no issues with bandwidth for AD/DFS etc. replication.
I will also likely be looking at installing a single Active Directory domain across both HQ and branch office, as I understand that modern day Microsoft best practices recommend steering away from multiple domains in a single forest except in exceptional circumstances.
My question is this...
If I maintain one domain across both sites (say company.com), how can I maintain a logical DNS separation between the two sites, (say for arguments sake dc1.london.company.com and dc1.birmingham.company.com)? Can this be done by structuring DNS in a certain way, without having to have a london.company.com and birmingham.company.com AD domain, one for each site?
Thank you in advance for any advice that can point me in the right direction!
Answer
You don't have different DNS namespaces for the two branches if they're in the same AD domain. There's no reason to. They would both be in the same DNS namespace as the parent. What reason would you have for two different DNS namespaces?
Also, avoid naming your AD domain "company.com" if that's also what your external website's name is. Name it something like "ad.company.com" or "internal.company.com". Having a split namespace will cause headaches.
No comments:
Post a Comment