• So here’s the situation:

    I’m working on a WordPress site for a friends company. I’ve had it on one of my domain names while working on it (I’m using BlueHost). My friends company has their current website on an in-house web server within their IT department. They said its pretty outdated so they signed up for a BlueHost account to start hosting there. Their domain name is thru GoDaddy.

    They were holding off on me launching their new site for about a week. So I had the WP site migrated from my BlueHost account to their new hosting account, which is also BlueHost. Someone did this for me by the way…and they have it setup on a temporary URL https://xxx.xxx.xxx.xxx/~(account name). The X’s are their IP address of there BlueHost account. So when I go to change the nameservers, their GoDaddy domain name would then point to their BlueHost hosting and the site should then display on their domain name.

    Today, I received the “go ahead” to change the nameservers to get their new site up. Turns out, once I did that, their company email server went down. They didn’t communicate with me about any of that stuff (which I don’t know much about anyways). After all this panic, they changed the nameservers back and eventually got their emails back up and running.

    Now what they’re IT team is telling me is they need to have the site load when you go to their IP address and they said they need to plug that IP into their internal web server and it should work. Does this sound right? What are mine/their options?

    Does anyone have background or knowledge about this stuff? Alot of this hosting and DNS stuff is still fairly new to me. Any help would be greatly appreciated!

Viewing 1 replies (of 1 total)
  • Were there emails set up on their old in house server or a different email server completely?

    If the prior, then as soon as the DNS for that domain was changed then it would change the records that handle all emails, which is probably why it broke.

    New email accounts would need to be set up on the new bluehost account which in turn will change all their settings if they have it hooked up to an email client, outlook for example.

    To leave the emails alone, you will need to change just the A record for the domain not the entire DNS.

    This will then point the domain to the new hosting but leave emails untouched.

    Options are to point to A record for the domain, and leave the DNS/MX record (handles email) alone, keeping the old server though.

    OR

    Set up the emails again on the new bluehost account and change DNS, thereford leaving the old server redundant.

    This is of course entirely based on my guess of how the company has their email set up, so finding that out would help.

    I also may have missed something so if anyone can provide a better solution then please feel free!

Viewing 1 replies (of 1 total)
  • The topic ‘WP Migration, Hosting, In-House Server, IP's, etc.’ is closed to new replies.