Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Wordpress error: Cannot write style-custom.css file Question Question
How to manage Wordpress Files through SFTP? Question Question

Question

Wordpress site won't load after URL change to domain

Posted July 6, 2017 4k views
WordPress

Hi,

I’m having an issue as well. I changed the ip address to my domain and I get this error.

This site can’t be reached

www.botflyer.com’s server DNS address could not be found.

Any ideas what might be the problem? I have another Wordpress site on DigitalOcean and the name servers setup is the same so I’m not sure why it’s not loading.

Thanks in advance for your help!

Kash

Add a comment
avkashpatel1
By:
avkashpatel1

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Wordpress error: Cannot write style-custom.css file Question Question
How to manage Wordpress Files through SFTP? Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
3 answers
hansen July 6, 2017

Hi @avkashpatel1

You’re not using DigitalOcean’s name servers with that domain, you’re using Google Domains.
So either you can control the DNS records via Google Domains, or you can change name servers to DigitalOcean and control DNS there.
If you just changed name server, then it can take up to 48 hours to fully work.

Reply Report
davidfavor July 6, 2017

Looks like your DNS is broken.

Here are your DNS Servers…

imac> dig +short botflyer.com ns
ns-cloud-b1.googledomains.com.
ns-cloud-b2.googledomains.com.
ns-cloud-b3.googledomains.com.
ns-cloud-b4.googledomains.com.

So independent of DNS propagation, if you hit these NS records directly for an A record, then your A record should most surely be returned + non of these NS servers return an A record for your domain… so chances are they never will…

imac> dig botflyer.com a @ns-cloud-b[1234].googledomains.com
<empty/nada/crickets chirping in the dead of night>

Since you’re using GoogleDomains.com for your DNS, you must login to their DNS facility + setup all your DNS records correctly.

When you can dig them, then all will be well.

Reply Report
clipartpig July 12, 2017

Thank you for responses. I had same trouble. I fixed:)

Reply Report

Related

Looking for something else?

Ask a new question Search for more help