I have a Windows Server 2008 R2 machine which is a domain controller under Active Directory: Domain Services and I want to also run quite a few things from this one machine. Mostly I'm learning how to hook everything up and don't really care too much about enterprise redundancy stuff.
Anyway, the issues I'm coming across now are that the AD: DS needs a DNS. We're hosting the DNS on this machine as well, on a different IP address. We have 8 addresses facing an internal network in the data center and then 8 addresses facing the Internet.
This is how I'd like to see things set up for each address. Every bullet is a separate address and use for it.
- Authoritative DNS for websites and internal machines and forwarding service for everything else. OCSP address for the certification authority.
- IIS for websites
Now, the problem that comes with this is managing all of the addresses things need to manage or listen on or ignore. It seems that the Windows DNS likes to just associate addresses automatically and give them the same domain name as whatever the DNS is running on, because it makes sense in large systems with a dedicated DNS. However, I want this machine to have different domains for almost every IP address and I really don't want the Windows DNS overwriting or remaking deleted A and AAAA records. It even adds the private IP addresses to the DNS, which really don't need to be there.
How can I better manage the different addresses and services? The DNS problem is my top priority right now and then after that, I'm not sure how to resolve the issue of managing multiple domains and the VPN from one machine on different addresses. It seems like since everything wasn't built to be run on one machine, it's going to be difficult. But I'm learning, so it's all interesting.
Any input here would be much appreciated.