I am getting an error message "Network unreachable: DNS issue" after
sitemap resubmition. The problem starts on 08 Nov 2008 when my site
was down for 2-3 hours. There is no reason for this error since I have
more than 3k uniq visitors a day. The problem is not only with my
sitemap but with all the internal pages. They ar in the 'Unreachable
URLs' section and marked as 'DNS issue'. I've tryed at least 15
sitemap resubmitions with the same result.
Judging from that error message, we haven't been able to reach your
DNS server since about Nov 8. This is a bit problematic, because after
a while the DNS information we have will be expired and we won't be
able to reach your server anymore. It might be that your hoster has
accidentally blocked Googlebot from accessing the DNS servers, so I
would get in touch with them to make sure that it's resolved before it
starts affecting all sites which use those DNS servers. If they have
any questions, feel free to point them to this thread and ask them to
post here.
The problem began a few days ago with a couple of sites but has now
spread to all the sites on our name servers, some of which have been
on sitemaps for years. Without fail we are seeing that ALL the sites
on the above DNS get the error and all the others (on different DNS)
are fine. Just for info here is a sample of some of the affected
sitemaps.
However this is not the end of the story - Last week we submitted a
new site (www.skisaintlary.com) to the sitemaps system and got the
same error - according to sitemaps no pages have been indexed as they
said - "Network unreachable: DNS issue - We couldn't communicate with
the DNS server when we tried to access the page." - Even though,
somehow, they successfully authenticated the site on sitemaps (http://
www.skisaintlary.com/googlebb8a12f6890f8ed2.html)
However looking at my user agent log files I see that we have had
visits from Google and others:
Bear in mind this a BRAND NEW SITE there is no legacy traffic here -
these figures come from AFTER we submitted it to sitemaps.
All this leads to only one conclusion - that Google-Bot uses different
Name Severs than Google-Sitemaps does, otherwise how could I have
verified the site? I even tried the Google translator system to get
access to the site without problems.
I have seen a lot of chatter about this subject but very little
substance. Lots of people have speculated about compliance issues,
server responses, redirects, code issues, xml formatting etc. ALL of
these people are missing the point - the clue is in the error "Network
unreachable" Googlebot is NOT EVEN SEEING the sitemaps! Any other
issues with individual sites are merely incidental.
THIS IS A DNS ISSUE PEOPLE !!!
I have spoken to the people who provide our name servers and they are
adamant that they have altered nothing either with the name severs or
with the routers that would block request from Googlebot (well, they
would, wouldn't they!) - The problem is that this is happening in the
black hole that is Google's internal workings and thus it's VERY hard
to provide evidence for what's going on.
Is there anyway to know exactly which name servers Googlebot is using?
At least that way we can see the problem for ourselves and then use
this for ammunition when speaking to our providers.
All this is, of course, based on the premise that, as you said "your
hoster has accidentally blocked Googlebot from accessing the DNS
servers" - If it ain't that...? There is only other plausible solution
I can come up with is that Googlebot ITSELF is having problems talking
to certain name servers.
> Judging from that error message, we haven't been able to reach your
> DNS server since about Nov 8. This is a bit problematic, because after
> a while the DNS information we have will be expired and we won't be
> able to reach your server anymore. It might be that your hoster has
> accidentally blocked Googlebot from accessing the DNS servers, so I
> would get in touch with them to make sure that it's resolved before it
> starts affecting all sites which use those DNS servers. If they have
> any questions, feel free to point them to this thread and ask them to
> post here.
> The problem began a few days ago with a couple of sites but has now
> spread to all the sites on our name servers, some of which have been
> on sitemaps for years. Without fail we are seeing that ALL the sites
> on the above DNS get the error and all the others (on different DNS)
> are fine. Just for info here is a sample of some of the affected
> sitemaps.
> However this is not the end of the story - Last week we submitted a
> new site (www.skisaintlary.com) to the sitemaps system and got the
> same error - according to sitemaps no pages have been indexed as they
> said - "Network unreachable: DNS issue - We couldn't communicate with
> the DNS server when we tried to access the page." - Even though,
> somehow, they successfully authenticated the site on sitemaps (http://www.skisaintlary.com/googlebb8a12f6890f8ed2.html)
> However looking at my user agent log files I see that we have had
> visits from Google and others:
> Bear in mind this a BRAND NEW SITE there is no legacy traffic here -
> these figures come from AFTER we submitted it to sitemaps.
> All this leads to only one conclusion - that Google-Bot uses different
> Name Severs than Google-Sitemaps does, otherwise how could I have
> verified the site? I even tried the Google translator system to get
> access to the site without problems.
> I have seen a lot of chatter about this subject but very little
> substance. Lots of people have speculated about compliance issues,
> server responses, redirects, code issues, xml formatting etc. ALL of
> these people are missing the point - the clue is in the error "Network
> unreachable" Googlebot is NOT EVEN SEEING the sitemaps! Any other
> issues with individual sites are merely incidental.
> THIS IS A DNS ISSUE PEOPLE !!!
> I have spoken to the people who provide our name servers and they are
> adamant that they have altered nothing either with the name severs or
> with the routers that would block request from Googlebot (well, they
> would, wouldn't they!) - The problem is that this is happening in the
> black hole that is Google's internal workings and thus it's VERY hard
> to provide evidence for what's going on.
> Is there anyway to know exactly which name servers Googlebot is using?
> At least that way we can see the problem for ourselves and then use
> this for ammunition when speaking to our providers.
> All this is, of course, based on the premise that, as you said "your
> hoster has accidentally blocked Googlebot from accessing the DNS
> servers" - If it ain't that...? There is only other plausible solution
> I can come up with is that Googlebot ITSELF is having problems talking
> to certain name servers.
> Would appreciate any help you can give.
> Tim
> On Nov 14, 12:30 pm, JohnMu wrote:
> > Hi Themza and welcome to the groups!
> > Judging from that error message, we haven't been able to reach your
> > DNS server since about Nov 8. This is a bit problematic, because after
> > a while the DNS information we have will be expired and we won't be
> > able to reach your server anymore. It might be that your hoster has
> > accidentally blocked Googlebot from accessing the DNS servers, so I
> > would get in touch with them to make sure that it's resolved before it
> > starts affecting all sites which use those DNS servers. If they have
> > any questions, feel free to point them to this thread and ask them to
> > post here.
> > Hope it helps!
> > John- Masquer le texte des messages précédents -
> > The problem began a few days ago with a couple of sites but has now
> > spread to all the sites on our name servers, some of which have been
> > on sitemaps for years. Without fail we are seeing that ALL the sites
> > on the above DNS get the error and all the others (on different DNS)
> > are fine. Just for info here is a sample of some of the affected
> > sitemaps.
> > However this is not the end of the story - Last week we submitted a
> > new site (www.skisaintlary.com) to the sitemaps system and got the
> > same error - according to sitemaps no pages have been indexed as they
> > said - "Network unreachable: DNS issue - We couldn't communicate with
> > the DNS server when we tried to access the page." - Even though,
> > somehow, they successfully authenticated the site on sitemaps (http://www.skisaintlary.com/googlebb8a12f6890f8ed2.html)
> > However looking at my user agent log files I see that we have had
> > visits from Google and others:
> > Bear in mind this a BRAND NEW SITE there is no legacy traffic here -
> > these figures come from AFTER we submitted it to sitemaps.
> > All this leads to only one conclusion - that Google-Bot uses different
> > Name Severs than Google-Sitemaps does, otherwise how could I have
> > verified the site? I even tried the Google translator system to get
> > access to the site without problems.
> > I have seen a lot of chatter about this subject but very little
> > substance. Lots of people have speculated about compliance issues,
> > server responses, redirects, code issues, xml formatting etc. ALL of
> > these people are missing the point - the clue is in the error "Network
> > unreachable" Googlebot is NOT EVEN SEEING the sitemaps! Any other
> > issues with individual sites are merely incidental.
> > THIS IS A DNS ISSUE PEOPLE !!!
> > I have spoken to the people who provide our name servers and they are
> > adamant that they have altered nothing either with the name severs or
> > with the routers that would block request from Googlebot (well, they
> > would, wouldn't they!) - The problem is that this is happening in the
> > black hole that is Google's internal workings and thus it's VERY hard
> > to provide evidence for what's going on.
> > Is there anyway to know exactly which name servers Googlebot is using?
> > At least that way we can see the problem for ourselves and then use
> > this for ammunition when speaking to our providers.
> > All this is, of course, based on the premise that, as you said "your
> > hoster has accidentally blocked Googlebot from accessing the DNS
> > servers" - If it ain't that...? There is only other plausible solution
> > I can come up with is that Googlebot ITSELF is having problems talking
> > to certain name servers.
> > Would appreciate any help you can give.
> > Tim
> > On Nov 14, 12:30 pm, JohnMu wrote:
> > > Hi Themza and welcome to the groups!
> > > Judging from that error message, we haven't been able to reach your
> > > DNS server since about Nov 8. This is a bit problematic, because after
> > > a while the DNS information we have will be expired and we won't be
> > > able to reach your server anymore. It might be that your hoster has
> > > accidentally blocked Googlebot from accessing the DNS servers, so I
> > > would get in touch with them to make sure that it's resolved before it
> > > starts affecting all sites which use those DNS servers. If they have
> > > any questions, feel free to point them to this thread and ask them to
> > > post here.
> > > Hope it helps!
> > > John- Masquer le texte des messages précédents -
> > - Afficher le texte des messages précédents -- Hide quoted text -
> > > The problem began a few days ago with a couple of sites but has now
> > > spread to all the sites on our name servers, some of which have been
> > > on sitemaps for years. Without fail we are seeing that ALL the sites
> > > on the above DNS get the error and all the others (on different DNS)
> > > are fine. Just for info here is a sample of some of the affected
> > > sitemaps.
> > > However this is not the end of the story - Last week we submitted a
> > > new site (www.skisaintlary.com) to the sitemaps system and got the
> > > same error - according to sitemaps no pages have been indexed as they
> > > said - "Network unreachable: DNS issue - We couldn't communicate with
> > > the DNS server when we tried to access the page." - Even though,
> > > somehow, they successfully authenticated the site on sitemaps (http://www.skisaintlary.com/googlebb8a12f6890f8ed2.html)
> > > However looking at my user agent log files I see that we have had
> > > visits from Google and others:
> > > Bear in mind this a BRAND NEW SITE there is no legacy traffic here -
> > > these figures come from AFTER we submitted it to sitemaps.
> > > All this leads to only one conclusion - that Google-Bot uses different
> > > Name Severs than Google-Sitemaps does, otherwise how could I have
> > > verified the site? I even tried the Google translator system to get
> > > access to the site without problems.
> > > I have seen a lot of chatter about this subject but very little
> > > substance. Lots of people have speculated about compliance issues,
> > > server responses, redirects, code issues, xml formatting etc. ALL of
> > > these people are missing the point - the clue is in the error "Network
> > > unreachable" Googlebot is NOT EVEN SEEING the sitemaps! Any other
> > > issues with individual sites are merely incidental.
> > > THIS IS A DNS ISSUE PEOPLE !!!
> > > I have spoken to the people who provide our name servers and they are
> > > adamant that they have altered nothing either with the name severs or
> > > with the routers that would block request from Googlebot (well, they
> > > would, wouldn't they!) - The problem is that this is happening in the
> > > black hole that is Google's internal workings and thus it's VERY hard
> > > to provide evidence for what's going on.
> > > Is there anyway to know exactly which name servers Googlebot is using?
> > > At least that way we can see the problem for ourselves and then use
> > > this for ammunition when speaking to our providers.
> > > All this is, of course, based on the premise that, as you said "your
> > > hoster has accidentally blocked Googlebot from accessing the DNS
> > > servers" - If it ain't that...? There is only other plausible solution
> > > I can come up with is that Googlebot ITSELF is having problems talking
> > > to certain name servers.
> > > Would appreciate any help you can give.
> > > Tim
> > > On Nov 14, 12:30 pm, JohnMu wrote:
> > > > Hi Themza and welcome to the groups!
> > > > Judging from that error message, we haven't been able to reach your
> > > > DNS server since about Nov 8. This is a bit problematic, because after
> > > > a while the DNS information we have will be expired and we won't be
> > > > able to reach your server anymore. It might be that your hoster has
> > > > accidentally blocked Googlebot from accessing the DNS servers, so I
> > > > would get in touch with them to make sure that it's resolved before it
> > > > starts affecting all sites which use those DNS servers. If they have
> > > > any questions, feel free to point them to this thread and ask them to
> > > > post here.
> > > > Hope it helps!
> > > > John- Masquer le texte des messages précédents -
> > > - Afficher le texte des messages précédents -- Hide quoted text -
> > - Show quoted text -- Masquer le texte des messages précédents -
> > Yes thats a good idea but unfortunately we don't control it, our
> > server provider does!
> > They are just saying "nothing to do with us" - If I knew which Name
> > Servers Googlebot uses then I could prove it to them (if that is the
> > issue).
> > Bottom line here is if I can Dig the Googlebot namesever for one of
> > our sites it will either say:
> > "Can't Find It" - in which case I have evidence for our hosts. or it
> > will say....
> > "Here is the IP" - in which case Googlebot has a problem.
> > Either way without knowing the DNS I can't test it.
> > Regards
> > Tim
> > BTW - don't even suggest changing Name Servers for our site - We have
> > 500+ using them!!
> > On Nov 17, 3:57 pm, webado wrote:
> > > Check the firewall. It must be blocking many Googolebots by IP or IP
> > > range.
> > > On 17 nov, 10:48, BuildArk wrote:
> > > > Hi John
> > > > Have to say I am getting the same problem - "Network unreachable: DNS
> > > > issue".
> > > > We have 30+ site using sitemaps to keep the index up to date. Of these
> > > > about 20 use our own nameservers:
> > > > The problem began a few days ago with a couple of sites but has now
> > > > spread to all the sites on our name servers, some of which have been
> > > > on sitemaps for years. Without fail we are seeing that ALL the sites
> > > > on the above DNS get the error and all the others (on different DNS)
> > > > are fine. Just for info here is a sample of some of the affected
> > > > sitemaps.
> > > > However this is not the end of the story - Last week we submitted a
> > > > new site (www.skisaintlary.com) to the sitemaps system and got the
> > > > same error - according to sitemaps no pages have been indexed as they
> > > > said - "Network unreachable: DNS issue - We couldn't communicate with
> > > > the DNS server when we tried to access the page." - Even though,
> > > > somehow, they successfully authenticated the site on sitemaps (http://www.skisaintlary.com/googlebb8a12f6890f8ed2.html)
> > > > However looking at my user agent log files I see that we have had
> > > > visits from Google and others:
> > > > Bear in mind this a BRAND NEW SITE there is no legacy traffic here -
> > > > these figures come from AFTER we submitted it to sitemaps.
> > > > All this leads to only one conclusion - that Google-Bot uses different
> > > > Name Severs than Google-Sitemaps does, otherwise how could I have
> > > > verified the site? I even tried the Google translator system to get
> > > > access to the site without problems.
> > > > I have seen a lot of chatter about this subject but very little
> > > > substance. Lots of people have speculated about compliance issues,
> > > > server responses, redirects, code issues, xml formatting etc. ALL of
> > > > these people are missing the point - the clue is in the error "Network
> > > > unreachable" Googlebot is NOT EVEN SEEING the sitemaps! Any other
> > > > issues with individual sites are merely incidental.
> > > > THIS IS A DNS ISSUE PEOPLE !!!
> > > > I have spoken to the people who provide our name servers and they are
> > > > adamant that they have altered nothing either with the name severs or
> > > > with the routers that would block request from Googlebot (well, they
> > > > would, wouldn't they!) - The problem is that this is happening in the
> > > > black hole that is Google's internal workings and thus it's VERY hard
> > > > to provide evidence for what's going on.
> > > > Is there anyway to know exactly which name servers Googlebot is using?
> > > > At least that way we can see the problem for ourselves and then use
> > > > this for ammunition when speaking to our providers.
> > > > All this is, of course, based on the premise that, as you said "your
> > > > hoster has accidentally blocked Googlebot from accessing the DNS
> > > > servers" - If it ain't that...? There is only other plausible solution
> > > > I can come up with is that Googlebot ITSELF is having problems talking
> > > > to certain name servers.
> > > > Would appreciate any help you can give.
> > > > Tim
> > > > On Nov 14, 12:30 pm, JohnMu wrote:
> > > > > Hi Themza and welcome to the groups!
> > > > > Judging from that error message, we haven't been able to reach your
> > > > > DNS server since about Nov 8. This is a bit problematic, because after
> > > > > a while the DNS information we have will be expired and we won't be
> > > > > able to reach your server anymore. It might be that your hoster has
> > > > > accidentally blocked Googlebot from accessing the DNS servers, so I
> > > > > would get in touch with them to make sure that it's resolved before it
> > > > > starts affecting all sites which use those DNS servers. If they have
> > > > > any questions, feel free to point them to this thread and ask them to
> > > > > post here.
> > > > > Hope it helps!
> > > > > John- Masquer le texte des messages précédents -
> > > > - Afficher le texte des messages précédents -- Hide quoted text -
> > > - Show quoted text -- Masquer le texte des messages précédents -
> > - Afficher le texte des messages précédents -- Hide quoted text -
Hi everybody!
We have axactly the same issue here, all of our sites pages are slowly
disappearing from google index. Started also on 8.nov..
As far as I discovered, we had some problems with DNS configuration,
as I found out on http://dnscheck.iis.se/. We had some problems with
PTR records and recursive lookups. Our DNS service company is solving
these issues right now.
I also checked your domains BulidArk, looks like all of them have some
DNS problems (misconfigured DNS server).
Could it be, that Google started dealing with domains which have badly
configured DNS servers on 8th? Any word about this from you, Google?
You should explain your errors a bit further that just simple "Network
unreachable: DNS error", so we don't loose time investigating
thousands of possibilities for this behaviour.
> The problem began a few days ago with a couple of sites but has now
> spread to all the sites on our name servers, some of which have been
> on sitemaps for years. Without fail we are seeing that ALL the sites
> on the above DNS get the error and all the others (on different DNS)
> are fine. Just for info here is a sample of some of the affected
> sitemaps.
> However this is not the end of the story - Last week we submitted a
> new site (www.skisaintlary.com) to the sitemaps system and got the
> same error - according to sitemaps no pages have been indexed as they
> said - "Network unreachable: DNS issue - We couldn't communicate with
> the DNS server when we tried to access the page." - Even though,
> somehow, they successfully authenticated the site on sitemaps (http://www.skisaintlary.com/googlebb8a12f6890f8ed2.html)
> However looking at my user agent log files I see that we have had
> visits from Google and others:
> Bear in mind this a BRAND NEW SITE there is no legacy traffic here -
> these figures come from AFTER we submitted it to sitemaps.
> All this leads to only one conclusion - that Google-Bot uses different
> Name Severs than Google-Sitemaps does, otherwise how could I have
> verified the site? I even tried the Google translator system to get
> access to the site without problems.
> I have seen a lot of chatter about this subject but very little
> substance. Lots of people have speculated about compliance issues,
> server responses, redirects, code issues, xml formatting etc. ALL of
> these people are missing the point - the clue is in the error "Network
> unreachable" Googlebot is NOT EVEN SEEING the sitemaps! Any other
> issues with individual sites are merely incidental.
> THIS IS A DNS ISSUE PEOPLE !!!
> I have spoken to the people who provide our name servers and they are
> adamant that they have altered nothing either with the name severs or
> with the routers that would block request from Googlebot (well, they
> would, wouldn't they!) - The problem is that this is happening in the
> black hole that is Google's internal workings and thus it's VERY hard
> to provide evidence for what's going on.
> Is there anyway to know exactly which name servers Googlebot is using?
> At least that way we can see the problem for ourselves and then use
> this for ammunition when speaking to our providers.
> All this is, of course, based on the premise that, as you said "your
> hoster has accidentally blocked Googlebot from accessing the DNS
> servers" - If it ain't that...? There is only other plausible solution
> I can come up with is that Googlebot ITSELF is having problems talking
> to certain name servers.
> Would appreciate any help you can give.
> Tim
> On Nov 14, 12:30 pm, JohnMu wrote:
> > Hi Themza and welcome to the groups!
> > Judging from that error message, we haven't been able to reach your
> > DNS server since about Nov 8. This is a bit problematic, because after
> > a while the DNS information we have will be expired and we won't be
> > able to reach your server anymore. It might be that your hoster has
> > accidentally blocked Googlebot from accessing the DNS servers, so I
> > would get in touch with them to make sure that it's resolved before it
> > starts affecting all sites which use those DNS servers. If they have
> > any questions, feel free to point them to this thread and ask them to
> > post here.
Let me know what happens with your sites. However this is still not
conclusive as yesterday I switched DNS on a site that had fallen off
sitemaps and now is back. The strange thing though is that this new
DNS throws errors too, even though the site successfully spidered!
Curious.
I have switched a few more DNS today - lets see what happens in the
morning.
You are right about the error codes too - I little more info on those
errors please Mr. Google!!
> Hi everybody!
> We have axactly the same issue here, all of our sites pages are slowly
> disappearing from google index. Started also on 8.nov..
> As far as I discovered, we had some problems with DNS configuration,
> as I found out onhttp://dnscheck.iis.se/. We had some problems with
> PTR records and recursive lookups. Our DNS service company is solving
> these issues right now.
> I also checked your domains BulidArk, looks like all of them have some
> DNS problems (misconfigured DNS server).
> Could it be, that Google started dealing with domains which have badly
> configured DNS servers on 8th? Any word about this from you, Google?
> You should explain your errors a bit further that just simple "Network
> unreachable: DNS error", so we don't loose time investigating
> thousands of possibilities for this behaviour.
> with regards,
> Urban
> On Nov 17, 4:48 pm, BuildArk wrote:
> > Hi John
> > Have to say I am getting the same problem - "Network unreachable: DNS
> > issue".
> > We have 30+ site using sitemaps to keep the index up to date. Of these
> > about 20 use our own nameservers:
> > The problem began a few days ago with a couple of sites but has now
> > spread to all the sites on our name servers, some of which have been
> > on sitemaps for years. Without fail we are seeing that ALL the sites
> > on the above DNS get the error and all the others (on different DNS)
> > are fine. Just for info here is a sample of some of the affected
> > sitemaps.
> > However this is not the end of the story - Last week we submitted a
> > new site (www.skisaintlary.com) to the sitemaps system and got the
> > same error - according to sitemaps no pages have been indexed as they
> > said - "Network unreachable: DNS issue - We couldn't communicate with
> > the DNS server when we tried to access the page." - Even though,
> > somehow, they successfully authenticated the site on sitemaps (http://www.skisaintlary.com/googlebb8a12f6890f8ed2.html)
> > However looking at my user agent log files I see that we have had
> > visits from Google and others:
> > Bear in mind this a BRAND NEW SITE there is no legacy traffic here -
> > these figures come from AFTER we submitted it to sitemaps.
> > All this leads to only one conclusion - that Google-Bot uses different
> > Name Severs than Google-Sitemaps does, otherwise how could I have
> > verified the site? I even tried the Google translator system to get
> > access to the site without problems.
> > I have seen a lot of chatter about this subject but very little
> > substance. Lots of people have speculated about compliance issues,
> > server responses, redirects, code issues, xml formatting etc. ALL of
> > these people are missing the point - the clue is in the error "Network
> > unreachable" Googlebot is NOT EVEN SEEING the sitemaps! Any other
> > issues with individual sites are merely incidental.
> > THIS IS A DNS ISSUE PEOPLE !!!
> > I have spoken to the people who provide our name servers and they are
> > adamant that they have altered nothing either with the name severs or
> > with the routers that would block request from Googlebot (well, they
> > would, wouldn't they!) - The problem is that this is happening in the
> > black hole that is Google's internal workings and thus it's VERY hard
> > to provide evidence for what's going on.
> > Is there anyway to know exactly which name servers Googlebot is using?
> > At least that way we can see the problem for ourselves and then use
> > this for ammunition when speaking to our providers.
> > All this is, of course, based on the premise that, as you said "your
> > hoster has accidentally blocked Googlebot from accessing the DNS
> > servers" - If it ain't that...? There is only other plausible solution
> > I can come up with is that Googlebot ITSELF is having problems talking
> > to certain name servers.
> > Would appreciate any help you can give.
> > Tim
> > On Nov 14, 12:30 pm, JohnMu wrote:
> > > Hi Themza and welcome to the groups!
> > > Judging from that error message, we haven't been able to reach your
> > > DNS server since about Nov 8. This is a bit problematic, because after
> > > a while the DNS information we have will be expired and we won't be
> > > able to reach your server anymore. It might be that your hoster has
> > > accidentally blocked Googlebot from accessing the DNS servers, so I
> > > would get in touch with them to make sure that it's resolved before it
> > > starts affecting all sites which use those DNS servers. If they have
> > > any questions, feel free to point them to this thread and ask them to
> > > post here.
I've been looking into this issue by looking at some of the sites
mentioned here. As far as I can tell, things should be back to normal
at the moment and there shouldn't be any long-term effects based on
this. Keep in mind that error/warning messages in Webmaster Tools will
generally remain visible for a while so it might take a bit before
they disappear there as well. I'll let you know more as I know
more :-).
Errors for domains with "Network unreachable: DNS error" are
disappearing one by one each day, it's getting better. As John said,
there are still "Errors for URLs in Sitemaps" and"Unreachable URLs"
for these cleared domains. I hope they'll be gone soon to.
So what was the reason? Our misconfigured DNS servers or something
else?
> I've been looking into this issue by looking at some of the sites
> mentioned here. As far as I can tell, things should be back to normal
> at the moment and there shouldn't be any long-term effects based on
> this. Keep in mind that error/warning messages in Webmaster Tools will
> generally remain visible for a while so it might take a bit before
> they disappear there as well. I'll let you know more as I know
> more :-).
i have the same problem,
this is the worst search engine problem i ever had, complete disaster!
description:
since November 8th
all websites from my hotgator reseller account are being deleted day
by day,
i asked hosting technicians but they say that is everything working
fine on my dns settings
a question for medismedis:
you say that the problem is getting better, have done anything about
it or google done? if yes can you describe us?
a question for John:
you say that we should be patient and everything is gonna be alright
by google or we have to change something?
> Errors for domains with "Network unreachable: DNS error" are
> disappearing one by one each day, it's getting better. As John said,
> there are still "Errors for URLs in Sitemaps" and"Unreachable URLs"
> for these cleared domains. I hope they'll be gone soon to.
> So what was the reason? Our misconfigured DNS servers or something
> else?
> with regards,
> Urban
> On Nov 19, 3:02 pm, JohnMu wrote:
> > Hi guys
> > I've been looking into this issue by looking at some of the sites
> > mentioned here. As far as I can tell, things should be back to normal
> > at the moment and there shouldn't be any long-term effects based on
> > this. Keep in mind that error/warning messages in Webmaster Tools will
> > generally remain visible for a while so it might take a bit before
> > they disappear there as well. I'll let you know more as I know
> > more :-).
We fixed ALL the problems with our DNS servers, but really don't know
if that helped, because John didn't say anything about the source of
the problem. These DNS servers were set up this way for years and the
problem arised on 8th of November.
My advice would be to check your DNS setup for your domains on
http://dnscheck.iis.se. If any errors occur, fix them (you or your
hosting provider).
> i have the same problem,
> this is the worst search engine problem i ever had, complete disaster!
> description:
> since November 8th
> all websites from my hotgator reseller account are being deleted day
> by day,
> i asked hosting technicians but they say that is everything working
> fine on my dns settings
> a question for medismedis:
> you say that the problem is getting better, have done anything about
> it or google done? if yes can you describe us?
> a question for John:
> you say that we should be patient and everything is gonna be alright
> by google or we have to change something?
> ns1.youhost.gr
> ns2.youhost.gr
> are my nameservers.
> thank you
> On Nov 20, 9:34 am, medismedis wrote:
> > Hi John and everybody!
> > Errors for domains with "Network unreachable: DNS error" are
> > disappearing one by one each day, it's getting better. As John said,
> > there are still "Errors for URLs in Sitemaps" and"Unreachable URLs"
> > for these cleared domains. I hope they'll be gone soon to.
> > So what was the reason? Our misconfigured DNS servers or something
> > else?
> > with regards,
> > Urban
> > On Nov 19, 3:02 pm, JohnMu wrote:
> > > Hi guys
> > > I've been looking into this issue by looking at some of the sites
> > > mentioned here. As far as I can tell, things should be back to normal
> > > at the moment and there shouldn't be any long-term effects based on
> > > this. Keep in mind that error/warning messages in Webmaster Tools will
> > > generally remain visible for a while so it might take a bit before
> > > they disappear there as well. I'll let you know more as I know
> > > more :-).
We have had the same problem since 7th November (has been fine since
May before that). This week the traffic has gone down significantly
since google has started de-indexing our pages.
We tried changing the dns (ns5.niris.co.uk to ns5.securedc.com)
yesterday as it was using a (reseller) alias which we thought google
might have suddenly stopped allowing? I think this is still in the
process of moving over...
All the "Network unreachable: DNS issue" have disappeared, things are
getting back to normal.
We still have a bunch of "Unreachable URLs" and "Errors for URLs in
Sitemaps", but the number of broken URLs is falling each day.
Obviously DNS server misconfiguration was the issue in our case. But
it is still unclear why all of this started happening on 7/8 of
November. John?
> We fixed ALL the problems with ourDNSservers, but really don't know
> if that helped, because John didn't say anything about the source of
> the problem. TheseDNSservers were set up this way for years and the
> problem arised on 8th of November.
> My advice would be to check yourDNSsetup for your domains onhttp://dnscheck.iis.se. If any errors occur, fix them (you or your
> hosting provider).
> with regards,
> Urban
> On Nov 20, 12:19 pm, Dimitris wrote:
> > Hi to all of you,
> > this forum is the oasis in the desert.
> > i have the same problem,
> > this is the worst search engine problem i ever had, complete disaster!
> > description:
> > since November 8th
> > all websites from my hotgator reseller account are being deleted day
> > by day,
> > i asked hosting technicians but they say that is everything working
> > fine on mydnssettings
> > a question for medismedis:
> > you say that the problem is getting better, have done anything about
> > it or google done? if yes can you describe us?
> > a question for John:
> > you say that we should be patient and everything is gonna be alright
> > by google or we have to change something?
> > ns1.youhost.gr
> > ns2.youhost.gr
> > are my nameservers.
> > thank you
> > On Nov 20, 9:34 am, medismedis wrote:
> > > Hi John and everybody!
> > > Errors for domains with "Networkunreachable:DNSerror" are
> > > disappearing one by one each day, it's getting better. As John said,
> > > there are still "Errors for URLs in Sitemaps" and"UnreachableURLs"
> > > for these cleared domains. I hope they'll be gone soon to.
> > > So what was the reason? Our misconfiguredDNSservers or something
> > > else?
> > > with regards,
> > > Urban
> > > On Nov 19, 3:02 pm, JohnMu wrote:
> > > > Hi guys
> > > > I've been looking into thisissueby looking at some of the sites
> > > > mentioned here. As far as I can tell, things should be back to normal
> > > > at the moment and there shouldn't be any long-term effects based on
> > > > this. Keep in mind that error/warning messages in Webmaster Tools will
> > > > generally remain visible for a while so it might take a bit before
> > > > they disappear there as well. I'll let you know more as I know
> > > > more :-).
|
