Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

if I setup a Windows Server 2008R2 instance on one of our servers and name it:

Is the 'normal' procedure to point a dedicated public IP address to it and then add a CNAME to the domain name?

So if a user were to want access remotely to the router then the full DNS name would resolve?

Sorry if this isn't making much sense, I don't fully understand the usual conventions of naming servers and their domains.

share|improve this question
up vote 4 down vote accepted

A name is a dynamic thing, and servers especially can have more than one. Take for instance a .NET web-app server such as used for Outlook Web Access. Depending on the roles it has, it can have any of the following names:

  • The AD name of the server itself (
  • The internal DNS name of the OWA server used for convenience (
  • The external DNS name of the OWA server used for outside logins (
  • The external DNS name in the MX record for (

DNS names are not one-to-one with servers. Servers in shared-hosting farms can have thousands of DNS names pointing to the same server.

As for the active directory DNS-domain, in my above example, the DNS domain '' may be completely unresolvable from the outside. Intentionally so, even. It prevents those tasty SRV records being used as a hacking hit-list.

In your case, DC01 should probably have a private address and not bother with a public one. Remote access to that would be done via public IP, probably proxied by way of a NAT gateway with a port-forward, and the DNS used there would be whatever you want it to be.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.