Google Webmaster tool error: Google couldn't access your site because of a DNS error


Anyone please help me get rid of this error at Google webmaster tools: Google couldn’t access your site because of a DNS error.

Timeout: Google couldn’t access your site because your DNS server did not recognize your hostname (such as

Its been their since last 5 days. My site:

I did changed few whois details and extended the validity of domain name.

If I can reach your site, Google should be able to reach it too.

If Google is having problems, my guess would be it’s less likely the DNS thing, but more the 192 Errors and 26 Warnings giving it trouble.

Those w3c validation errors are since long.
Why DNS errors now then ?

When did you do the changes and when did Google say that had problems caused by DNS?

I guess you shouldn’t have this problem if you simply updated personal details in your WhoIs registry but if you changed the DNS servers, it can take up to 48 h to propagate worldwide.

1 Like

Try testing your site with Google Search Console:

Google Search Console → Crawl → Fetch as Google

Also try temporarily renaming .htacces file.

True. However, some time back, Google started reporting it couldn’t access the robots.txt file on one of my sites. I could, as could anybody else I asked. Bing had no issues, only Google. I’d made no changes to the file or the hosting since the site first went up, and Google had previously had no problems. This went on for several weeks, and nothing I tried had any effect. (e.g. deleting the file and uploading it again.) Then the problem vanished as mysteriously as it appeared. I never did get to the bottom of it.

1 Like

Then I guess we should ask Google direclty because they’re the only ones that can check what’s behind.

It is strange enough that Google can’t access a robots.txt file but I assume that a DNS error is, mainly, caused by the registry company or wrong data input. That doesn’t mean that it may not be Google’s fault. Maybe is a bad cofiguration in one of their gateways or firewalls. That could also cause errors accesing some websites.

I just went to my GWT and I had a DNS error message too. And I haven’t touched my domain name or host for years.

The closest explanation that might apply that I could see was “a temporarily over loaded name server”

Oh… You got the solution for it then ?

If it’s a temporary problem with the name server it’s mostly out of my control and not much I can do but be patient and wait.

I will keep an eye on it and if it persists I guess I could contact my host and pester them about it. But for now I’m not going to do anything about it.

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.