Split DNS for Active Directory

Hi experts,

I planned to upgrade our AD for Enterprise Usage, AD before just used for Exchange mail account only. Upgrading also mean we going to move from Windows 2008 to Windows 2008 R2 - taking advantage of single sign in AD as in feature all our applications will be authenticated using AD.

My bos asked me to split out the DNS from AD server so it can be on its own and served others as well (computers that not joining domain). Currently we have DNS server that runs on Linux machine. This new DNS will served as replacement to this Linux DNS.

AD also must be allow to dynamically write on this DNS, plus DNS admin can also do manual entry.

How can I do this? What I know is new DNS must be a domain controller. Does this mean that all user information also duplicated to this new DNS server? If in this case, do RODC plays any role here to reduce this new DNS burden?

Any idea, please? Any notes I can refer to?
LVL 13
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

elawadConnect With a Mentor Commented:
You can install DNS on a domain controller and makes it active directory integrated DNS server which means that it will hold all the records of you hosts computers and it will replicate this record in case you have another DNS server while active directory is replicating. or else you can configure it as holding primary zone this will makes him replicate solely to your secondery DNS zone if it exists.
KaffiendConnect With a Mentor Commented:
DNS is not going to impact performance much (unless you are still running a 10-year old server, I guess)

You don't need RODC (you might want a RODC for other reasons, but DNS' impact on performance shouldn't be a concern)

And, every AD Domain Controller server should be running DNS.  DNS is one of the cornerstones of Active Directory.

A Windows-based DNS server should have no trouble at all servicing DNS requests from Linux or MAC clients - not a concern

When you make a member server a Domain Controller, you will be asked (assuming it is not already running DNS) if you want to install DNS as well - just say yes if prompted.

You can use Linux DNS but it will complicate your solution and not provide any more advantages over using Windows DNS. Given the option I would always use Windows DNS in this scenario.

Is there any reason why your boss does not want to use Windows DNS apart from being able to service machines that are not in the domain? If this is in the only reason it might be a good idea to suggest to him that from a machine point of view they will not notice any difference from a Linux or Windows DNS server.

You get great integration with dynamic DNS updates and therefore do not need to setup all the AD type srv records that are needed when you install a new DC.
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

HI khairi,

Any feedback on the comments added?


khairilAuthor Commented:
Sorry guys,

Last 3 weeks I have waiting emails from EE but nothing comes, but at last an email form EE saying that this is abandon question. I wonder is something wrong with my email system.

Anyway guys, give me sometime to look on your suggestion. I've duplicated my current AD infra into virtualization.
khairilAuthor Commented:
Thanks guys.
All Courses

From novice to tech pro — start learning today.