thesamet wrote:It is impossible to connect to pythonchallenge.com by entering its ip in the url, since it is a shared IP (or a virtual host, or something).
Yeah, you've got a name-based virtual host. There are basically three types of virtual hosts:
- web-site per IP address, where a server uses IP aliases and has multiple IP's assigned to a NIC.
- web-site per port, where you run each web-site on a different port, but all on the same IP (not very common...)
- multiple web-sites per IP address. In this case, the web-server somehow needs to know which web-site to serve up. It determines this by looking at the HTTP Host: header sent by the browser. For this to work, you need to visit the site by its name, otherwise the web browser just sends the IP in the HTTP Host: header and the web-server doesn't have anyway to know which virtual host to serve.
So the real question is, why can't you visit pythonchallenge by hostname? Are you getting a DNS failure? I just did a cursory check of pythonchallenge's DNS and I don't see any problems. The .com servers delegate the DNS for pythonchallenge.com to ns1.bluehost.com and ns2.bluehost.com. The glue records for ns1.bluehost.com and ns2.bluehost.com look fine and each of those servers appears to be returning the correct answer for pythonchallenge.com when asked... so I'm not sure what's causing your DNS problems.
Can you get to http://www.bluehost.com/