Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

Google WMT DNS errors

         

night707

5:55 am on May 22, 2016 (gmt 0)

10+ Year Member Top Contributors Of The Month



Some of our sites are now suffering now from DNS errors though the settings have been the very same for all of them since years.

Domains are not getting crawled and were taken out of the index.

Even Google dns tools say that everything is fine and their bots have no problem with reading robots.txt and to confirm server connectivity.

not2easy

2:45 pm on May 22, 2016 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



They might be looking for a verification file, a .txt file they tell you how to get here: [support.google.com...]

night707

7:29 pm on May 22, 2016 (gmt 0)

10+ Year Member Top Contributors Of The Month



all domains have a verified status since ages and WMT confirms robots.txt and server connectivity ...

robzilla

8:12 pm on May 22, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Is it possible your nameservers have (or have had) intermittent issues?

lucy24

11:14 pm on May 22, 2016 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Some of our sites are now suffering now from DNS errors though the settings have been the very same for all of them since years.

Domains are not getting crawled and were taken out of the index.

Even Google dns tools say that everything is fine and their bots have no problem with reading robots.txt and to confirm server connectivity.

There seems to be a step missing. Who's telling you there is a DNS problem? Google itself (speaking out of both sides of its mouth, apparently) or someone else?

Entire domains? How many? In order to be taken out of the index, they must once have been in the index. What time span are we talking about?

night707

5:53 am on May 23, 2016 (gmt 0)

10+ Year Member Top Contributors Of The Month



Thanks Lucy,
WMT started to report DNS errors on April 5 and it has affected 4 out of 14 domains, all with exactly the same dns settings on the same server. All of these domains were properly indexed sine ages.