So as the title says, I need to promote a standalone Win2008R2 server to a Domain Controller, and I don't a DNS Server (I think), as there will be no clients connected to the domain, it will be only used for Remote Desktop Services. Yes, I know, it's considered bad practice to install other roles on the DC, but in this case, it's necessary.
Do I need to install the DNS Server, and if I do, how to make it as transparent as possible?
EDIT: Seems that I need to install the DNS Server, so I can I configure it not to mess up my entire domain?
For example:
The server I need to promote is rdc.mydomain.com, and it has an A entry to it's IP in the current DNS, while other servers under mydomain.com are running Linux and don't need to know anything about this Windows box. The domain uses a third-party DNS and all edits and updates need to be done via a separate web page, our servers don't have write/update access.
Simple answer, YES you need to install DNS Server. Otherwise you will not be able to install AD and installation will simply fail.
Active Directory depends on DNS, this is not negotiable at all. When you promote the server to be a DC, the wizard will ask if you want to install the DNS Server role on it as well, this is the easiest way to do it.
Why not create a subdomain within that domain purely for AD (ad.mydomain.com)? Or create your own internal only domain for the Windows box (eg org.my).
There's no need to mess with the existing domain just for AD.
I managed to solve this by creating a VM into a local-only network and assigning that machine to be a DC to a local domain
mydomain.local. This way the RD server can connect to it, but it's separate from the rest of the network and won't affect any other services/servers.