Home / server / Questions / 172571
Accepted
markratledge
Asked: 2010-08-20 16:46:32 +0800 CST

Is something wrong with DNS when the domain resolves but the IP address throws a 404?

  • 772

When the domain resolves OK for a website, but the IP throws a 404 at the site, is this a DNS problem?

Kind of complicated: I have a client with 3 domains. All three point to one hosting account. Two are pointed at that host, but are not the root of the WordPress install. One domain is for WordPress; and that domain also has some subdomains configured in DNS. (Network Solutions hosting and domains)

I've advised them that the two domains should be domain forwarded, not pointed at the hosting account, and that might be part of the problem.

Where do I start trying to figure this out? What else do I need to question or investigate?

Edit 8/19/10:

Thanks for the responses, and everyone had suggested host headers, but I don't know what those are or where I would find those settings. The hosting is called nsHosting Shared (Small-Unix). I can't find any more details on it. Nothing out of the ordinary in .htaccess.

This is the DNS for the domain that Wordpress is installed under (no CNAME records):

Host                                 IP
www                     206.188.192.100  Network Solutions Hosting
@ (None)                206.188.192.100  Network Solutions Hosting
* (All Others)          206.188.192.100  Network Solutions Hosting
grafton.mydomain.com       216.161.227.32 
mail.mydomain.com         24.111.147.85 
remote.mydomain.com     24.111.147.85
domain-name-system ip wordpress

4 Answers

  1. Best Answer

    No, it's not a DNS problem. It's a web server configuration problem. The solution could be as simple as adding host headers to each web site but we'll need more specifics from you regarding your web server\site configuration.

    • 3

  2. Sounds more like an HTTP server issue. Check how hostnames are used in your configuration. I use this "feature" to point users that don't have a Host: header to a specific DocRoot in my configuration.

    • 2

  3. Most likely you have virtual hosts/host headers set up if the sites are all on the same IP and port.

    • 2

  4. Kicking quite an old thread, but I ran into a similar issue. After fiddling around while attempting to install an SSL certificate, my server was also throwing 404s when accessed via the IP address, whereas all worked fine via the FQDN. Sadly, a number of our older apps access the server via a hard-coded IP address . .

    The issue was solved by adding a binding in IIS (8.5, Windows Server 2012 R2) with a blank Host Name value. You can only add one in two steps:

    • Add a new http binding and enter a Host Name, then press OK,
    • Edit the thing and remove the Host Name, then press OK again.

    In one pass it won't work because the OK button will remain dimmed.

    • 1