Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Well here comes the situation.

I used to have CompanyA for webhosting. (The hosting plan was a shared one). I decided to change the hosting provider and transfer my website to CompanyB, (exclusive IP).

The issue that i face is that my webpage is now displayed in two different IP addresses. So i decided to turn-off the website served by the CompanyA.

Now the problem is that my database driven website, served by CompanyB, is not driven anymore, although i have added the A record with the ipaddress of the database. (The database is served by dedicated db's server).

So, what am i doing wrong here?

share|improve this question
You mention using a CNAME pointing at the database's IP address. If the DNS record is truly pointing at an IP address instead of another name, you should use an A record. – Shane Meyers Jan 23 '10 at 5:47
Sorry about mistyping. The records is A. – gipap Jan 25 '10 at 8:05

When you moved from CompanyA to CompanyB, did you move your database with it? If you did, and it's running and everything, make sure that you updated your application's configuration to point to the new host at CompanyA.

If you originally configured it with the IP address instead of domain name, that would explain the symptoms.

share|improve this answer
No i did not move the database, while swiching from CompanyA to B. The database is hosted in different IP Address – gipap Jan 22 '10 at 13:45
Is the database hosted with company A? – Matt Simmons Jan 22 '10 at 14:51
Yes the database is hosted with company A – gipap Jan 25 '10 at 8:02
I think that's your problem. Either company A turned off your database, or your database is set to let you log in from a specific address (or address block), and you've changed to Company B. Talk to Company A and see what the specific issue is. – Matt Simmons Jan 25 '10 at 12:08
It definitely sounds like this is the source of the problem in one way or another. If the database is accessible, it could also be something like the database permissions that the app uses not allowing for the remote connection (ie, MySQL's user@host). – Paul Kroon Jun 1 '10 at 23:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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