PDA

View Full Version : How should I config my server given 3rd party (easyDNS) DNS?



adrianboyko
09-22-2003, 11:08 AM
I do all my DNS through easyDNS, so my domain (adrianboyko.com) isn't handled by WestHost even though my website is hosted here.

This was never a problem in the past. I had a dedicated IP here at WestHost and I simply created DNS records at easyDNS to point to the dedicated IP I had here.

But this doesn't seem to work with WestHost 2.0. I'm guessing that this is because I no longer have a dedicated IP address. The IP I get when I ping www.adrianboyko.westhost.com is 69.36.161.59. Diagnosing the problem with "curl", I get the following results:

curl -v http://69.36.161.59/
Empty response from server.

curl -H "host: adrianboyko.westhost.com" -v http://69.36.161.59/
Returns the page, as expected.

curl -H "host: adrianboyko.com" -v http://69.36.161.59/
Empty response from server.

So I guess the IP addr is shared on the basis of the "host" header. Is there any way I can configure my virtual server so that my adrianboyko.com domain is recognized in addition to the adrianboyko.westhost.com subdomain that's already being correctly dispatched? I've tried setting ServerName in httpd.conf, but that doesn't seem to do the trick.

Any suggestions? Is this the sort of config issue that's outside my virtual server, and only fixable by WestHost?

Adrian

FZ
09-22-2003, 11:39 AM
Both adrianboyko.com and www.adrianboyko.com work for me - they resolve to 216.220.40.244 (ns2.easydns.com), and going to each forwards me to adrianboyko.westhost.com (resolves to 69.36.161.59 which does not have a reverse DNS). What that probably means is that your new IP address isn't dedicated (or that you have to use WestHost nameservers for that to work). What package do you have?

On a side note, why would you want to still use non-WestHost nameservers when you more or less (now) have the same level of functionality through the 2.0 Site Manager (subdomains, etc.)?

adrianboyko
09-22-2003, 10:59 PM
Thanks for responding, Design. EasyDNS allows an "URL forwarding" option which I'm currently using to get around the problem on the WestHost side. So (as you've already noticed) going to http://www.adrianboyko.com/ results in easyDNS forwarding the request to http://www.adrianboyko.westhost.com, and WestHost correctly responds to such requests (presumably because they include "host: www.adrianboyko.westhost.com" in the request).

The "curl" examples in my previous posting all used URLs based on the WestHost machine's IP address instead of URLs based on DNS names because I wanted to eliminate DNS and URL forwarding from the discussion.

If we ignore all DNS and URL forwarding issues, the question still remains: What need to be configured so that the following give the same result...

curl -H "host: adrianboyko.westhost.com" -v http://69.36.161.59/

curl -H "host: adrianboyko.com" -v http://69.36.161.59/

I'm on the "Starter" plan, which doesn't list "dedicated IP" as one of the features. I don't remember what the plan details were when I signed up a couple years ago, but I told them I needed a dedicated IP and they gave me 64.33.30.199. I'm sure this detail was lost when my account was transitioned to WestHost 2.0.

FZ
09-23-2003, 08:03 AM
If you previously paid for a dedicated IP and you no longer have one (seems as if you don't) you should send in a support request. You might also want to ask them to make adrianboyko.com the "primary account domain" (just a suggestion). Hope you get it sorted out.