Our company environment is growing rapidly and I'm in the process of upgrading our Domain Controllers, but before I do I wanted to do a quick sanity check to make sure I'm still doing everything the best way possible.
Focusing on my primary HQ site, I have 3 domain controllers (2 virtual, 1 physical) all running Windows Server 2008 R2. I wish to migrate to Windows Server 2012 R2. I don't believe in 'upgrading' Windows, I always prefer 'migration' to keep the servers/environments clean of upgrade artifacts.
The two virtual DCs provide all DNS services for all of my workstations and member servers. Workstations get the DNS addresses through DHCP options while all member servers have the DNS server IPs configured static.
Question:
Is it still normal to use your domain controllers as the DNS resolvers for all of your workstations and servers, or should I create new dedicated DNS servers?
Question:
Is it good practice to use the real IPs of the domain controllers on workstations and servers for DNS resolvers or should I use virtual IPs/load balancing?
Answer
Is it still normal to use your domain controllers as the DNS resolvers
for all of your workstations and servers, or should I create new
dedicated DNS servers?
I have 2000+ clients in my company and 4 domain controllers. 2 of them are also acting as DNS Server with no issue for 4 years now.
Is it good practice to use the real IPs of the domain controllers on
workstations and servers for DNS resolvers or should I use virtual
IPs/load balancing?
Once again, for 2000+ clients i use real DNS resolver IP with no issues.
I provide these metrics as a kind of "reference". Depending on your number of clients, DNS load could be higher and my topology could not applies to you...But IMHO you can go safely with DC+DNS
As stated by Microsoft :
Most often, you will install DNS servers on all domain controllers
But i let you read the full article here
No comments:
Post a Comment