Hosting Transfer
-
Hello, I’ve been working transfer my hosting from BlueHost to GoDaddy. My Domain Selsea.fr is registered with WordPress.com. I’ve verified the DNS settings with GoDaddy and it’s been over 72 hours since we’ve made the changes.
Our Name servers are correctly set too.
What am I missing? Why is our site still down? Please help.
Thanks
WP.com: Yes
Jetpack: No
Correct account: YesThe blog I need help with is: (visible only to logged in users)
-
-
Hi there, I have checked on the
selsea.frdomain, and the name servers are showing as pointing to Godaddy, but the site does not come up if I try and visit it. Since the name servers and set to Godaddy, you will need to contact them about getting the domain connected to the site you have there. They should be able to help with that, and possibly with the migration of any content from Bluehost. -
I have, they keep referring me back to the an issue with the DNS. They look at the DNS records and say everything is correct, and that it’s an issue with wordpress.com.
I’m sure you can understand my frustration as it’s been 4 days my site doesn’t work. -
Hi there, @melaniegaillard!
I completely understand the frustration. To clarify, the issue is not actually on WordPress.com’s end. Here are the current name servers set on the domain:
ns81.domaincontrol.com ns82.domaincontrol.comThat means you manage DNS with GoDaddy. These name servers were just set yesterday. DNS propagation can take up to 72 hours but is typically a lot faster than that. DNS propagation is the process of updating the information about a domain name across all the DNS servers on the internet. When you update the DNS settings for your domain name, such as changing the IP address or nameservers, it takes time for the changes to propagate across all the DNS servers on the internet.
Saying that, this site is now loading for me. Here is what I see when I visit your domain:

If you still are having issues, make sure to confirm with your new host that your DNS records look good and your domain is pointing correctly to your site with them.
-
Thanks for your help, go daddy documentation was incomplete and so the nameservers were set to ns1.godaddy.com. They were unable to find the issue and told me the issue was with the dns.
I’ve since found the correct nameservers and it worked within a few minutes as they usually do.
This issue is resolved, thank you for the the help!
-
-
- The topic ‘Hosting Transfer’ is closed to new replies.