devereandpartners
asked on
Will my Active Directory DNS conflict with external DNS servers
Hello all,
I am about to start setting up Active Directory on Windows 2008 in the coming weeks. My setup will be a standard AD procedure with 2 DC Servers and a few weeks later down the line creating a child DC in another country, all connected together.
I am planning to use the company's own domain as the forest name for example company.com. Now this domain already exists as has a mailserver, web server hosted with a 3rd party company and I plan to keep it this way.
My question is, will using the same domain affect my AD Dns with the public Dns worldwide. Keep in mind I also plan to connect a domain server set up in another country. If problem arises I would just use company.local instead but I rather use the proper one to be more streamlined.
I hope my question was understandable and I thank you fin advance for any feedback given. Cheers!
I am about to start setting up Active Directory on Windows 2008 in the coming weeks. My setup will be a standard AD procedure with 2 DC Servers and a few weeks later down the line creating a child DC in another country, all connected together.
I am planning to use the company's own domain as the forest name for example company.com. Now this domain already exists as has a mailserver, web server hosted with a 3rd party company and I plan to keep it this way.
My question is, will using the same domain affect my AD Dns with the public Dns worldwide. Keep in mind I also plan to connect a domain server set up in another country. If problem arises I would just use company.local instead but I rather use the proper one to be more streamlined.
I hope my question was understandable and I thank you fin advance for any feedback given. Cheers!
According to Microsoft this isn't the best practice. However, I have seen it done plenty of times without any problems.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Your name choice has nothing to do with being "streamlined". Your *internet* presence has nothing at all to do with your *management* domain. You should keep these apart, so as to avoid any possible confusion which is which. Note that even if you're using a suffix like .local, you can still run Exchange or whatever with your normal email addresses, and you can even add an alternate UPN suffix so that users can, for example, logon to your AD domain.local using their email address user@domain.com.
The following article is not limited to SBS, it applies to most AD installations:
The Domain Name System name recommendations for Small Business Server 2000 and Windows Small Business Server 2003
http://support.microsoft.com/kb/296250
The following article is not limited to SBS, it applies to most AD installations:
The Domain Name System name recommendations for Small Business Server 2000 and Windows Small Business Server 2003
http://support.microsoft.com/kb/296250
You should not use the same name of your internal AD domain as your external domain name. It is bad practice and create confusion as well as create extra work and troubleshooting down the road...why bother.
Why not just come up with a unique name, like oBdA suggested, you can always create UPN suffix and allow user to logon with username same as their email address which user will have less to complain with.
Why not just come up with a unique name, like oBdA suggested, you can always create UPN suffix and allow user to logon with username same as their email address which user will have less to complain with.
ASKER
Thanks alot for all the feedback. I will take the most secure option and go with company.local Will avoid needless complication for just adding .com. Cheers