I am not sure if you did this step or not… But you might have to run````
a2ensite mydomain.com

There is sites-available, and sites-enabled. I am pretty sure that apache includes all the vhost files in sites-enabled. So you have to enable the site by using the command above and then restart apache with````
service apache2 restart

.

Lets see, I'm running a public website, listed in public Domain Name Servers, running on not one but two public web servers (while being moved).

Yet when I want help, I'll mask any and all public information so that at best people who know how to help will have to play 20 questions getting to the root of the problem.

Yeah, that's a great idea.

Can't be toooooooo paranoid about divulging those PUBLIC DOMAIN NAMES AND IP's.

So try this:

or this

<*>

and see if that helps.

mwisner - no problems there

vonskippy - I really didn't think anyone would have an issue making head or tails of it but I have uncensored everything (except the e-mail address) to help you.

And yes… the interwebs are a scary place ;)

Seems to be working. From here, http://www., vote., and bare comparemycandidates.com all point to 50.116.53.66. Visiting any of the sites in a browser redirects me to the same page: https://vote.comparemycandidates.com/accounts/login/

Regarding your questions:

1. No, this is not necessary. It is your choice whether to use Linode's nameservers or continue using GoDaddy.

Edit: Your NS records should reflect the same servers designated with your domain registrar. Right now this points to ns##.domaincontrol.com (GoDaddy).

2. You only need to set up name records on Linode if you are going to switch to using Linode's nameservers. In that case, you would need to create records for all names you want to resolve - it's not possible to split a domain and have some names on GoDaddy's DNS and some on Linode's.

3. Not sure if there are any rules against having a bare example.org as your reverse DNS. I would generally suggest using the name that your server thinks it is called (see what hostname -q gets you).

In your /etc/hosts, you should not have more than one line with the same IP address. If you need more names, simply add them to the end of the existing line. For your purposes, I really don't think you need to have anything other than the default localhost and ipv6 entries in there anyway.

Thanks for the suggestions and answers.

I'm not certain we are on the same page, however. When I type in the subdomain, vote.comparemycandidates.com, I want to arrive there or some page that's part of it (depends on if you're logged in or not). However, if I type in the root domain, comparemycandidates.com, I want to arrive at that site, the WordPress one that I am trying to migrate, not the subdomain.

I'm not sure what I'm missing but there's gotta be some broken link in the chain of pointing and dns records. /shrug :?

I guess another way to put it would be: I have two websites on the same linode. One is a subdomain of the other. How do I make it so visitors can visit both websites under the same IP?

It doesn't matter if it's a 'subdomain' or a completely different domain: Apache's logic for routing the request is the same:

1) Find all of the stanzas with the best match for the interface the request arrived on

2) Out of that set, find a stanza with an exactly-matching ServerName or ServerAlias, or find one that matches a wildcard, or find the first one it learned about.

What does the following command say: apache2ctl -S

Also, it appears that you aren't running Apache. nginx is what's issuing the redirect:

rtucker@witte:~$ curl -I http://comparemycandidates.com/

HTTP/1.1 301 Moved Permanently

Server: nginx/0.7.65

Date: Fri, 13 Jul 2012 19:44:10 GMT

Content-Type: text/html

Content-Length: 185

Connection: keep-alive

Location: https://vote.comparemycandidates.com/

So, please post your nginx configurations as well.