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

I am setting up a server to host an application which will be on a subdomain, let's say "". "" is hosted on a completely different server, points to a different IP, etc.

Do I want the FQDN for my new server to be based off the domain, such as "", or based off of the subdomain, such as ""?

Does it even make any particular difference? The application is a LAMP stack application which should be connecting to some sort of external mailserver.

share|improve this question
Is the application dependent on the host name? If not, then name the server whatever you like. – joeqwerty Oct 10 '13 at 15:39
I don't believe it is. I added a few application specific details above if they help clarify, but overall, what in broad strokes would make an application FQDN dependent? – Dave Stern Oct 10 '13 at 16:23
up vote 2 down vote accepted

This doesn't make a lick of difference. However, one useful naming strategy is to assign your machines name records that are broadly indicative of their main use, ie, web01,web02,db01,mail01 and then use CNAME records to point the names of particular services to those machines, for example www, ftp, mysql.

So, for example, in your case, you could create an A record giving an IP to

You could then create a CNAME record that points to the name

One day when you decide to host application2 on you can create a CNAME that points to the name

If you ever need to move the application to a different server, say, you can just change the CNAME record for to point to instead of

Check out

share|improve this answer
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.