Iam trying to point domain to a different dedicated Linux server.

What I've already done:

  1. On server1 changed A record to an IP of server2 (IP which has been already assigned to subdomain)
  2. Created package and account on server2 for sub-domain
  3. I am getting error when I visit sub-domain (I have already tried ipconfig /flushdns):

If you feel you have reached this page in error, please contact the web site owner:

webmaster@ads.pixfuture.net It may be possible to restore access to this site by following these instructions for clearing your dns cache. If you are the web site owner, it is possible you have reached this page because:

The IP address has changed. There has been a server misconfiguration. The site may have been moved to a different server. If you are the owner of this website and were not expecting to see this page, please contact your hosting provider.


You can check what record is being returned with "nslookup <hostname>" in a command window. While flushing your local DNS cache is a good idea, if your configured nameserver(s) still have the old record cached, it will return that until the TTL expires.

  • Well. Its interesting because nslookup shows main IP address of the server2. What you saying I did it right? – Alex Feb 8 '11 at 2:44
  • By the way FTP access works. I'm lost now. Why then sub-domain shows error? – Alex Feb 8 '11 at 2:47
  • In the case that the host is resolving to the correct address, there's likely a mismatch between the configuration of the web server and the host name. In the case of an Apache web server, the vast majority of hosting is based on name-based virtual hosts. This works by inspecting the the request from the browser for a Host header. It uses this to match against a specific configuration statement in the web server which will identify the correct configuration statements to use. If the configuration does not match the Host header, the web server will serve the request with the default host name. – mcmeel Feb 8 '11 at 2:48
  • @mcmeel/ Its now showing when i type 'www.subdomain.mydomain.com', but without 'www.' still same thing. However, I've made 2 A records on server1 'www.subdomain' and 'subdomain'; I guess its just matter of time as you said. Lets see whats gonna happen. Ill write back here as soon as I get this thing to work – Alex Feb 8 '11 at 3:04
  • If you've verified that both the www.subdomain.mydomain.com and the subdomain.mydomain.com hosts are correctly resolving to the correct IP address, I suspect the web server is configured to recognize the www'ized host name, but does not recognize the non-www address. In the Apache world, the ServerAlias allows configuration of a second host name for a virtual server statement. It sounds like you're using a hosting solution that abstracts all the web server configuration, so I apologize that the Apache references may not be entirely helpful. – mcmeel Feb 8 '11 at 3:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.