Ok, I think I’ve got it. If someone else has a better understanding or explanatin of how CNAME entries work, please chime in! BTW, this explanation conflicts with my previous response, so please ignore my prevous post unless you want to make fun of me!
So CNAME entries work for DNS resolution for server IP addresses and mail addresses. You’re using it for webserver IP address resolution.
You have a CNAME of ww2 pointing to greddin.net - something like this:
ww2 CNAME greddin.net
My understanding of what this does is when the browser goes to the resolve ww2.greddin.com, it gets the CNAME record back. It then does another lookup for greddin.net and gets back the A record pointing to the IP address of your DreamHost server. Now it sends a request to port 80 of the machine at that IP address with an http host header of “host: ww2.greddin.com”. This totally confuses DreamHost’s server because you haven’t told it anything about ww2.greddin.com. This is consistent with your observations.
I don’t think you’re going to be able to get this to work out well with a CNAME record for reasons I’ll detail at the end of this post.
Here are your two choices for getting ww2.greddin.com to work:
- Host ww2.greddin.com at GoDaddy with a redirect, mirror, or cloak to www.greddin.net.
- Host ww2.greddin.com at DreamHost with a redirect, mirror, or cloak to www.greddin.net.
Option 1 has the benefit of not requiring you to enter any IP addresses manually and so you’re immune to DreamHost changing the IP addresses. Option 2 has the benefit of working even when GoDaddy web hosting is down but name service is up.
Let me know which one of these two options you want and someone here (maybe even me!) will be able to give you detailed instructions on the steps to achieve it.
Why do I think the CNAME solution won’t work to get DNS resolution for ww2.greddin.com’s IP address? It’s because there’s no absolutely correct server name to put into the CNAME record. What you need is to put in a server name that always resolves to the IP address of ww2.greddin.com at DreamHost. But because DreamHost potentially assigns different IP addresses to each domain and subdomain, there’s no guarantee that ww2.greddin.com will share an IP address with any particular other hostname. Yes, it’s true. ww2.greddin.com and greddin.com may have different IP addresses!
This post ended up being way more complicated than I originally thought it would and I apologize for that…
Free unique IP and $67 off with promo code [color=#CC0000]FLENSFREEIP67[/color] or use [color=#CC0000]FLENS97[/color] for $97 off. Click here for more options