dns/nameservers changed. it worked, but now it doesn't work
-
Hi
I just changed my blog from wordpress.com to wordpress.org, hosting via bluehost. My wordpress.com domain has had its dns info changed so it points to my new host (at bluehost) it worked a few hours ago, but now, whenever I go to myloveofmornings.com, I am redirected to the wordpress.com blog.Do you have any idea what might be wrong? It’s ange that it worked and then stopped working.
Thomas
The blog I need help with is: (visible only to logged in users)
-
Hi Thomas,
Sometimes it takes awhile for changes like that to work their way around the internet. A hosting tool shows your site is now at Bluehost. A DNS checker showed your site changes have propagated throughout the world (except for Pakistan).If you’re still seeing the WordPress.com hosted site, try flushing your computer’s DNS: https://www.whatsmydns.net/flush-dns.html
-
Thanks, that sounds good.
I also seem to be having some issues with my ssl certificate for the domain. Do you think that could be related?
I got an email from google control panel telling me this. Is this something that ought solve itself, or does it sound like something unrelated to the dns stuff?
I do get warnings opening my site telling me that the ssl certificate is unsure -
Hi there,
Name server changes can take up to 72 hours to fully propagate, and I see your domain’s was changed less than 24 hours ago, so the process might still be busy. Please try clearing your browser and DNS cache as @micawbr suggested, and if that doesn’t work give it another day and try again.
As for the SSL, that’s normal. The moment you pointed your domain away from us, the SSL certificate we issued for your domain was revoked. However, websites using SSL place a command in your browser via what’s called a HSTS header which tells your browser to always load your site over https. If you no longer have a SSL certificate on your domain, that can lead to security warnings.
The HSTS header should expired within another day or two, and then those warnings will go away, though of course you can also prevent those warnings by adding a new SSL certificate to your site at your new hosting provider. I know Bluehost supports free SSL certificates from LetsEncrypt, though they might require you to be on a specific hosting plan to use such a certificate.
- The topic ‘dns/nameservers changed. it worked, but now it doesn't work’ is closed to new replies.