New IP address but same physical hosting

[Tommybs]

Hi,

Not sure if this is the best forum for this but it relates to domain name.

I have a dedicated server with a number of domains on with 1 IP address.

Recently I've had the need to add a 2nd SSL certificate for a domain (having previously used 1). As such I needed to purchase an additional IP address. Now I've correctly associated my domain to the new IP address according to my hosts documentation and I've updated the domain with the ip on my server control panel. Whenever I now go to my domain.com address however I am presented with a blank site. All the files physically exist and if I connect via SCP to the new ip, it shows all the files from the old one.

All the DNS records (A name etc) all seem to be pointing to the new correct IP. I'm not too familiar with all the different types of DNS but for the life of me I can't understand why my site appears as if it is blank. Can anybody direct me to anything obvious to check?

[jdMorgan]

Did you 'define' the new IP address in the server configuration, and move this site's file into the filespace defined for the server on that IP address? I don't know how to put this more clearly, since the wording and functions of 'control panels' vary, and I don't know what kind of server you're on, but there are three steps:

1. Define a new IP-based virtual server.
   
2. Point that virtual server to a "DocumentRoot" defining the filespace for that virtual server.
   
3. Point the DNS record for that virtual server's domain to the new IP address.
   

It sounds like one of these steps --either #1 or #2-- has not been done (or done correctly).

BTW, that page may not be truly blank -- Do a View->Page Source in your browser to see if it has any html headers on it that may give you additional information -- It's not likely, but possible.

Also, check the server's HTTP response headers with a server headers checker (the Live HTTP Headers add-on for Firefox/Mozilla is handy), and make sure you're getting a reply from a server that appears to be yours. If you're hosted on IIS and the HTTP response says it's Apache, then that would be a string indication that the DNS isn't right (or hasn't yet propagated).

Neither of these two suggestions are 'highly useful' or closely-targeted at your problem, but might give you a hint if something is drastically wrong.

Jim

[Tommybs]

Hey, thanks for replying. There is a page there but it's just a default index.htm, not something I have made.
I'm running the site apache and using plesk if that information is helpful.

With regards to points 1 and 2. Are these things I have to setup in my httpd.conf file?

[Tommybs]

Just an update here (not sure if it's worth moving to the apache forum) but sometimes it seems to find my site and other times it doesn't. Could this just be a time thing relating to change of ip or should it be fine? $_SERVER['SERVER_ADDR'] is returning the new ip, but sometimes it fails to find the pages resulting in a 404. I've tried adding bits to httpd.conf but not sure if it's correct