Setting Up Subdomains in Linode and Apache

I’ve been using Linode for a few months to host about a dozen websites and I’ve been very happy with the experience. I have found the documentation at Linode to be clear and concise, especially when it comes to setting up multiple sites using a standard, Ubuntu-based LAMP (Linux, Apache, MySQL, PHP) configuration.

I decided to take one of the sites to the next level and add a subdomain. (An example of a primary domain is while a subdomain would be the ‘blog’ in Unfortunately, Linode’s library and other documents was less than clear about all of the steps.

My goal here is to explain, step by step, how to add a subdomain to your Linode service. I suppose this could work for any Ubuntu-based LAMP stack, but this may have some Linode-specific information.

**NOTE: My DNS services are managed at Linode, so I’ll assume you have done the same thing yourself.

First, we will tell the server what to do with traffic coming to the address.

  • Log into the Members section of Linode ( and find the Linode you want to add a subdomain to. Make a note of the IP Address (you will use this later). If you’re like most users, you will only have one Linode listed.
  • Next, open the DNS Manager at Linode by clicking ‘DNS Manager’ at the top. This should take you to a page that has at least one domain listed.
  • Select the domain you want to add a subdomain to. This will take you to a screen that lists several options. Mine lists SOA Record, then NS Records, MX Recods, then A/AAAA Records. Under the listed A/AAAA Records, click ‘Add a new A/AAAA Record’. **(UPDATE: I’ve read that one user had a problem getting this to work with an A Record, but was able to get it to work using the CNAME Record. I don’t believe it should matter, but if you’re having problems, you may want to use the CNAME.)**
  • You will be taken to a page with a form that says, ‘Add/Edit an A Record’. In the ‘Hostname:’ field, enter the name of your subdomain ‘blog’, ‘shop’, or ‘xyz’ could be examples. In the ‘IP Address:’ field, enter the IP address you made note of in the first step of this document. Click ‘Save’.
  • You will be taken back to the previous page. I click ‘Render’ at the bottom. I don’t know that it does anything, but it doesn’t seem to hurt. (***UPDATE*** Since this was written, it seems as though Linode has changed their DNS system. I don’t see the ‘Render’ button any more. Also, the look of the DNS system has changed. The end result should be the same, but you may see something slightly different than what I mention here.)

That wasn’t that difficult, was it? Well, now we get to go into dealing with actually setting up the subdomain on the Apache side.

Setting Up Apache
Setting up a subdomain is similar to setting up a normal domain following the guide found at, but there are a few changes that need to be made.
You will need to open an SSH connection to your Linode. I assume you know how to do this because if you didn’t, you probably wouldn’t be using Linode for your hosting solution.
Once you’ve connected via SSH, navigate to Apache’s sites-available directory. In the example given by Linode (and the default location upon a standard Apache2 installation), you can type (the # is just a prompt, do not type the # sign):

# cd /etc/apache2/sites-available
If you run the command

# ls

You will see the sites you’ve defined so far. You will need to create another site titled, where xyz is the subdomain of your choosing. You can do this by either copying an existing, working site definition or by creating a new file. I usually copy an old site using:

# cp

Now enter the command

# nano

You should see a box with text similar to:

<VirtualHost *:80>
DocumentRoot /srv/www/
ErrorLog /srv/www/
CustomLog /srv/www/ combined
Change the following lines as such:
DocumentRoot /srv/www/
It should now look like this:
<VirtualHost *:80>
DocumentRoot /srv/www/
ErrorLog /srv/www/
CustomLog /srv/www/ combined
What we have done is created a new server that notices that a user is coming to and it now points the user to a different directory (note xyz at the end of the line in the DocumentRoot section).
Exit out of that screen by typing control-x. You will be prompted to save the file, so click Y for Yes, then hit enter when it prompts you with the file name (it should be your
Now we create the directory the subdomain will read from:
# mkdir -p /srv/www/
Now we need to tell Apache to enable the site. Type:
# a2ensite
Then refresh Apache to know what’s going on:
# /etc/init.d/apache2 reload
You’re Done!

It may take anywhere from an hour or so to a day for the subdomain to propagate through the DNS system. I errantly assumed it would be immediate because DNS was managed by Linode, but it took about an hour for it to respond to my browser.

Help Keep This Site Going
If you found value to this article, please consider donating a dollar or two to help cover the cost of managing this site.

Alternately, if you’re interested in becoming a Linode user, please use this affiliate link before creating a Linode account.

32 thoughts on “Setting Up Subdomains in Linode and Apache

  1. Zander,
    I’m glad it was helpful. This is one of those things that is so frustrating to figure out, but once you know how to do it, you shake your head and think, “what was all the fuss about?”

  2. Thanks a lot for this guide! It is exactly what I was looking for. This should be on the Linode Library by the way, I am sure a lot of Linode users will benefit from it.

    Anyway, good job David.

  3. Unbelievably helpful! I had no idea how to point a folder to a sub-domain. Previously I could only find out how to create the sub-domain or do some weird redirection from a folder to sub-domain with htaccess…did that even make sense? Regardless….your walkthrough was perfect..Thanks Mr Podley!

  4. Exactly what I was looking for. I have just done it so have to wait for it to propagate to see if it works. I do have a quick question which I was not sure about.
    you put this
    but then when you said “it should look like this” you put


    In my file i just put the as I was unsure which was correct. It was a tad confusing at that moment but apart form that it was great.

  5. Thanks, this was helpful. Having just recently purchased a VPS, I had no idea how subdomains were handled – your post helped me realise I had to edit the zone files with my registrar. Obvious, but different to how I used to have to do it!

  6. Hello David,

    As far as I know I the setup I have now is exactly as you have described. The only difference is that I used other sites (which were definitly not as clear as yours).

    When I go to: “” , The page can not be found and i go directly to a search page with some search results

    However when i go to: “” it works perfectly.
    To make it even weirder, the main domain: “” works perfectly in: “” and “” , and is defined in exactly the same way as: “” is defined.

    SUBdomain: (in a seperate “” file in: “/etc/apache2/sites-available/” )

    DocumentRoot /srv/www/
    ErrorLog /srv/www/
    CustomLog /srv/www/ combined

    The main domain: “” is defined exactly as above in “/etc/apache2/sites-available/” only the name is “” and of cours in stead of “” is “”

    The domain name is registerd @ godaddy, in the godaddy zone-file “A-record” I routed the “rock” subdomain to “111.222.333.444”

    Again “http://red…” works perfect BUT “…” does NOT.

    Do you have any idea? (thanks for the turorial!)

  7. Sorry, in my post above somehow the brackets where omitted:

    …content as described above

  8. ( VirtualHost 111.222.333.444 )

    …content as described above


    replace paranteses whith brackets

    Sorry for “spamming”, there is no edit button…again my apolagies

  9. This post helped me immensely. I am new to server configuration, and was having an issue where my subdomains where conflicting with my regular site. Both sites would work, but people typing “” would be routed to “” unless they used the “www”. It ended up being that I was setting the virtual host configuration as:


    instead of what it should be:


    Thanks David!

  10. Thank you! Great post – nice and clear. Only just started using linode the other day. Really pleased with it so far!

  11. Thank you so much for this guide! Spent half an hour going through the library and forums and your post got me through the whole thing in 5 minutes! 😀

  12. Thank you! I agree with Kay. The Linode library was thin on subdomain details. It’s a simple process, but not necessarily intuitive.

  13. Hi

    How long does it take for the sub domains to propagate? I have been waiting for a couple of days now. I can access my main domain:

    but my subdomain:

    is still not accessible. I have disabled the default site. My domain is managed by linode’s domain manager. I dont know if I am doing something wrong. Can you please help. I am very new to this.

  14. I think I have figured out my mistake, in A/AAA records i had added the hostname as when i read you post again i figured out that i have to enter just “test” i have made the changes now, waiting to see if it opens up in the browser.

  15. In the /etc/apache2/sites-available file for the subdomain, did you change the DocumentRoot item to reflect a different directory? If did, have you enabled the site and refreshed Apache? (a2ensite followed by /etc/init.d/apache2 reload)

  16. Pingback: Setting up a Wordpress Website on Linode | Ramblings

  17. Pingback: Activating subdomain breaks my OpenCart | Open Cart Know How

  18. Pingback: DNS: make point to www/site/ – segmentfault

Leave a Reply

Your email address will not be published. Required fields are marked *