Now, I’ve got the DNS entries for domain.tld and sub.domain.tld both pointing to the same IP address (my webserver)… with the vhosts setup as above, the webserver is supposed to be able to determine which site the user is trying to access via information in the request, right?
I’ve got sites-enabled/default linked to sites-available/default (default is the text file)… there’s really no difference to having each vhost in a separate file is, there?
I changed all of the DNS settings to an “A” record to an IP address - before, they were just being forwarded. I’m not sure how it is really different, but it is.
If you’re having problems with 1&1 dns not working, just ask them to “reset” your account. It refreshes everything. Happened to me with a couple of clients.
Everything is working well now, thanks for your help MiG.
Follow-up question:
Now that I’m segregating my sites by subdomain, I’m out of subdomains!
My cheapo domain-registration only package at 1and1.com only gives me 5 subdomains - is this common practice, or are there free methods to get unlimited subdomains out there? I read somewhere that GoDaddy.com gives you unlimited subdomains.
Hmm, the 1and1 control panel will let me use a different set of nameservers (I can input whatever I want)…
But if I point domain.tld at a different nameserver, will that new nameserver also have control of sub.domain.tld and all the other possible subdomains?
What would really rock for me, is if I could have *.domain.tld all routed my way, and then have my server determine the routing. Like foo.domain.tld goes to this location, foo2.domain.tld goes to another location, and www.domain.tld, and anythingelseyoucanpossiblythinkof.domain.tld goes to the default location.