> So far I've wasted an hour, trying to get my 5 out of 17 sites re-re-
> re-verified and gave up.
> Since you know which sites you've screwed, why don't you fix them
> automatically or manually.
> Your problem should not become my problem and take a lot of my time to
> fix.
> If you can't or won't fix my sites, I'm happy to just stop using your
> dubious tools!!!
> On Mar 28, 1:14 am, JohnMu wrote:
> > Hi everyone!
> > I just wanted to give a short heads-up that we're aware of the issue
> > with site verification in Webmaster Tools. The team is working on it,
> > so you should all be able to take a deeper look into your site's
> > indexing through Webmaster Tools soon!
> > If your site was unverified, it will generally have no impact on any
> > settings or statistics in your account. They will all be back once
> > your site is re-verified.
> > I'm sorry for the disruption and hope to see you all in our chat
> > tomorrow!
My hostig ISP is ipower.com/.net and just to let anyone else know that
is using their service that has this problem. They are moving to a
new platform and they were the first ones I suspected when I had this
problem. On 03/14 my host could not be found and I reported the
problem and it was fixed. I suspect they didn't add all my DNS info
back in.
Nice tool. It's been awhile for me that I've been involved in any
network stuff (I'm an old buck) and appreciate the info.
I'll forward your info to them and as I mentioned earlier, you have to
tell them what the problem is before you can get them to fix it.
> Same Glue Looks like the A records (the GLUE) got from the parent zone
> check are different than the ones got from your nameservers. You have
> to make sure your parent server has the same NS records for your zone
> as you do.I detected some problems as follows:
> For ns1.ipowerdns.com the parent reported: ['66.96.142.103'] and your
> nameservers reported: ['66.96.142.102', '66.96.131.28']
> For ns1.ipowerweb.net the parent reported: ['66.96.142.103'] and your
> nameservers reported: ['66.96.131.116', '66.96.142.103']
> Missing nameservers reported by parent FAIL: The following nameservers
> are listed at your nameservers as nameservers for your domain, but are
> not listed at the parent nameservers (see RFC2181 5.4.1). You need to
> make sure that these nameservers are working.If they are not working
> ok, you may have problems!
> ns2.ipowerdns.com
> ns2.ipowerweb.net
> Either error is plausible with such a dns setup.
> Talk to your hoster to fix the dns.
> You also need to have all the correct namesevers in your domain
> registry - they have to agree with those provided by the hoster.
> On Mar 28, 11:16 pm, HCL wrote:
> > Here's a little more input for the powers to be:
> > My responses to try to verify varies:
> > Verification status: NOT VERIFIED
> > Last attempt Mar 28, 2008: We were unable to verify your file due to a
> > server timeout.
> > Verification status: NOT VERIFIED
> > Last attempt Mar 28, 2008: We encountered an error looking up your
> > site's domain name.
> > If it's software it would be consistent. The DNS lookup code is
> > simple and the Sofware Engineers will not find the problem.
> > I say this because every delay is causing me money and I anticipate
> > the SEs won't find it and we will be left out in the cold. Time is of
> > the Essense!
> > I realize there are many reasons via the posts for NOT VERIFIED caused
> > by user or configuration errors, internet response times, server
> > activity, etc., but in the end of this there will be a number of
> > webmasters that will still have a consistent error and the fault will
> > erroneously lie at our ISP..
> > My suggestion for those left behind would be to find common ground;
> > If it still persists we should setup a separate post and if we could
> > establish the origination Google IP and path we go through we could
> > isolate and identify where the problem may be.
> > It's been my experience, we will have to tell them what the problem is
> > before they will resolve it. You know the old finger pointing game and
> > we suffer.
> > FYI - my domain is headcoverleash,com
> > If anyone knows the actual Google IP the webmaster host originates
> > from we can trace the path and look for any common paths for those
> > still experiencing the problem.
> > On Mar 28, 7:04 pm, HCL wrote:
> > > Thank $,
> > > You know these problems could be caused by hardware/routers
> > > malfunctions at Google or or on their path out.
> > > Intermittent hardware problems will drive everyone crazy.
> > > After the software engineers say there is no problem, look to the
> > > hardware. Check the router or link errors.
> > > On Mar 28, 6:18 pm, $e0Guy wrote:
> > > > Now that I think about it, I would have to agree with HCL in the
> > > > possibility that other issues are arising as a result of this latest
> > > > problem. We are getting intermittent "errors" in some of our sitemaps
> > > > now that were perfectly fine previously.
> > > > If Google's system thinks there are problems with our sitemap.xml file
> > > > then the possiblity exists this will affect how Google processes and
> > > > makes use of that sitemap.xml file
> > > > One day it shows as no errors, next it shows 4 errors, the next it's
> > > > fine, and no changes on our part.
> > > > Again this is not the case with the majority of our sites, but for a
> > > > few newer sites it is.
> > > > On Mar 28, 6:11 pm, HCL wrote:
> > > > > John,
> > > > > I beg to differ. There is a major impact, not just showing
> > > > > statistics. This error seems to have caused a delay for Google to
> > > > > visit an index and update to a site. My site has not been updated
> > > > > since 03/11 and I have made major changes that are not reflected in
> > > > > search results. A side error to this is when a sitmape is updated,
> > > > > Google stopped reindexing the site. My sitemap shows no URL's indexed
> > > > > down from 10 to none.
> > > > > I have stop showing in the number 1 position and all the way back to
> > > > > 50 on a search that is term incusive of my domain name and previous
> > > > > search terms..
> > > > > My Google Base items no longer show in search product results or even
> > > > > in the tools that I have base items in myr account menu.
> > > > > I would say there are many relationships to this problem and hope you
> > > > > will understand that is has serious implicattion and pursue these
> > > > > relationships I've outline.
> > > > > Many people saw this NOT VERIFIED problem.
> > > > > One should be concerned that there seems to be no obvious way to
> > > > > contact webmaster technical support to report a problem.
> > > > > Maybe someone could show me how, but it's not obvious to me.
> > > > > If others have experienced these similar implication, it would
> > > > > demonstrate there are other problems created. Check your positions,
> > > > > producs and results.
> > > > > On Mar 27, 11:14 am, JohnMu wrote:
> > > > > > Hi everyone!
> > > > > > I just wanted to give a short heads-up that we're aware of the issue
> > > > > > with site verification in Webmaster Tools. The team is working on it,
> > > > > > so you should all be able to take a deeper look into your site's
> > > > > > indexing through Webmaster Tools soon!
> > > > > > If your site was unverified, it will generally have no impact on any
> > > > > > settings or statistics in your account. They will all be back once
> > > > > > your site is re-verified.
> > > > > > I'm sorry for the disruption and hope to see you all in our chat
> > > > > > tomorrow!
Same problem here. My site hasn't been crawled since 3/18, and I
uploaded a sitemap on 3/19. I am back to being verified, however, so
hopefully it will just take a little time for googlebot to revisit my
site. I have since deleted my sitemap in the hopes that the bot will
visit sooner instead of pulling info directly from my sitemap.
Googlebot did d/l my sitemap on 3/25.
> I beg to differ. There is a major impact, not just showing
> statistics. This error seems to have caused a delay for Google to
> visit an index and update to a site. My site has not been updated
> since 03/11 and I have made major changes that are not reflected in
> search results. A side error to this is when a sitmape is updated,
> Google stopped reindexing the site. My sitemap shows no URL's indexed
> down from 10 to none.
> I have stop showing in the number 1 position and all the way back to
> 50 on a search that is term incusive of my domain name and previous
> search terms..
> My Google Base items no longer show in search product results or even
> in the tools that I have base items in myr account menu.
> I would say there are many relationships to this problem and hope you
> will understand that is has serious implicattion and pursue these
> relationships I've outline.
> Many people saw this NOT VERIFIED problem.
> One should be concerned that there seems to be no obvious way to
> contact webmaster technical support to report a problem.
> Maybe someone could show me how, but it's not obvious to me.
> If others have experienced these similar implication, it would
> demonstrate there are other problems created. Check your positions,
> producs and results.
> On Mar 27, 11:14 am, JohnMu wrote:
> > Hi everyone!
> > I just wanted to give a short heads-up that we're aware of the issue
> > with site verification in Webmaster Tools. The team is working on it,
> > so you should all be able to take a deeper look into your site's
> > indexing through Webmaster Tools soon!
> > If your site was unverified, it will generally have no impact on any
> > settings or statistics in your account. They will all be back once
> > your site is re-verified.
> > I'm sorry for the disruption and hope to see you all in our chat
> > tomorrow!
Just check my sites, seems like John and his squad has fixed this
problem now. Just re-verify those sites using html and it works now.
Anybody else still has the issue?
> I just wanted to give a short heads-up that we're aware of the issue
> with site verification in Webmaster Tools. The team is working on it,
> so you should all be able to take a deeper look into your site's
> indexing through Webmaster Tools soon!
> If your site was unverified, it will generally have no impact on any
> settings or statistics in your account. They will all be back once
> your site is re-verified.
> I'm sorry for the disruption and hope to see you all in our chat
> tomorrow!
I agree. We love Goolge and their corporate stance of "Don't be evil".
Clearly in this case, Google needs to up their takes on customer
services either a message in Webmaster Central or pointing everybody
to the right venue for information. But it also points out a
interesting thing that is regardless of how advanced Google's
technology or "cloudy" they are on cloud technology, the google troops
and webmaster are always two camps. On Goolge's side, they probably
never realized how serious the problem and consequence (very serious)
and wide-spread this problems (only a few did get to this forum) has
caused to most of us in webmasters camp, and from webmaster's camp, we
completely rely on google being right in the first place. That's when
this problem arises, I do see a lots of folks here spending times and
frustration fixing potential issues on their end without even a thread
of "uhmmm, this could be Google's fault!" . There is a Googline in
between. We all need to reach out....
> > I haven't heard of thousands or tens of thousands of users with this
> > problem.
> RIGHT! If most people who use the Webmaster Tools system don't know
> to check the forums, which most do NOT, and the Google "Message" tab
> on the Tools Dashboard says "no messages", then of course you wouldn't
> have heard of tens of thousands with the problem.
> Have you looked through all of the Googles Groups? There are dozens
> of other threads from users all over the place who are reporting the
> problem who don't know or think to use this specific group forum.
> And as for the vast majority of people having this problem have it NOT
> be a Google issue - I don't buy that for a second. The odds of such a
> coincidence - people all over the world, all of a sudden, over the
> past four days, having the exact same problem, and oh, by the way, at
> the same exact time, Google's got a code issue that just happens to be
> the cause of this problem for a tiny fraction of us?
I am not sure what else to try, I checked the DNS with the link that
Webado kindly gave. Looks ok to me .. but I could be wrong as I am
not too sure when it somes to that technical side.
> I agree. We love Goolge and their corporate stance of "Don't be evil".
> Clearly in this case, Google needs to up their takes on customer
> services either a message in Webmaster Central or pointing everybody
> to the right venue for information. But it also points out a
> interesting thing that is regardless of how advanced Google's
> technology or "cloudy" they are on cloud technology, the google troops
> and webmaster are always two camps. On Goolge's side, they probably
> never realized how serious the problem and consequence (very serious)
> and wide-spread this problems (only a few did get to this forum) has
> caused to most of us in webmasters camp, and from webmaster's camp, we
> completely rely on google being right in the first place. That's when
> this problem arises, I do see a lots of folks here spending times and
> frustration fixing potential issues on their end without even a thread
> of "uhmmm, this could be Google's fault!" . There is a Googline in
> between. We all need to reach out....
> On Mar 28, 4:31 pm, $e0Guy wrote:
> > Webado,
> > On Mar 28, 4:00 pm, webado wrote:
> > > I haven't heard of thousands or tens of thousands of users with this
> > > problem.
> > RIGHT! If most people who use the Webmaster Tools system don't know
> > to check the forums, which most do NOT, and the Google "Message" tab
> > on the Tools Dashboard says "no messages", then of course you wouldn't
> > have heard of tens of thousands with the problem.
> > Have you looked through all of the Googles Groups? There are dozens
> > of other threads from users all over the place who are reporting the
> > problem who don't know or think to use this specific group forum.
> > And as for the vast majority of people having this problem have it NOT
> > be a Google issue - I don't buy that for a second. The odds of such a
> > coincidence - people all over the world, all of a sudden, over the
> > past four days, having the exact same problem, and oh, by the way, at
> > the same exact time, Google's got a code issue that just happens to be
> > the cause of this problem for a tiny fraction of us?
> Just check my sites, seems like John and his squad has fixed this
> problem now. Just re-verify those sites using html and it works now.
> Anybody else still has the issue?
> Yang S.
> On Mar 27, 11:14 am, JohnMu wrote:
> > Hi everyone!
> > I just wanted to give a short heads-up that we're aware of the issue
> > with site verification in Webmaster Tools. The team is working on it,
> > so you should all be able to take a deeper look into your site's
> > indexing through Webmaster Tools soon!
> > If your site was unverified, it will generally have no impact on any
> > settings or statistics in your account. They will all be back once
> > your site is re-verified.
> > I'm sorry for the disruption and hope to see you all in our chat
> > tomorrow!
> My hostig ISP is ipower.com/.net and just to let anyone else know that
> is using their service that has this problem. They are moving to a
> new platform and they were the first ones I suspected when I had this
> problem. On 03/14 my host could not be found and I reported the
> problem and it was fixed. I suspect they didn't add all my DNS info
> back in.
> Nice tool. It's been awhile for me that I've been involved in any
> network stuff (I'm an old buck) and appreciate the info.
> I'll forward your info to them and as I mentioned earlier, you have to
> tell them what the problem is before you can get them to fix it.
> > Same Glue Looks like the A records (the GLUE) got from the parent zone
> > check are different than the ones got from your nameservers. You have
> > to make sure your parent server has the same NS records for your zone
> > as you do.I detected some problems as follows:
> > For ns1.ipowerdns.com the parent reported: ['66.96.142.103'] and your
> > nameservers reported: ['66.96.142.102', '66.96.131.28']
> > For ns1.ipowerweb.net the parent reported: ['66.96.142.103'] and your
> > nameservers reported: ['66.96.131.116', '66.96.142.103']
> > Missing nameservers reported by parent FAIL: The following nameservers
> > are listed at your nameservers as nameservers for your domain, but are
> > not listed at the parent nameservers (see RFC2181 5.4.1). You need to
> > make sure that these nameservers are working.If they are not working
> > ok, you may have problems!
> > ns2.ipowerdns.com
> > ns2.ipowerweb.net
> > Either error is plausible with such a dns setup.
> > Talk to your hoster to fix the dns.
> > You also need to have all the correct namesevers in your domain
> > registry - they have to agree with those provided by the hoster.
> > On Mar 28, 11:16 pm, HCL wrote:
> > > Here's a little more input for the powers to be:
> > > My responses to try to verify varies:
> > > Verification status: NOT VERIFIED
> > > Last attempt Mar 28, 2008: We were unable to verify your file due to a
> > > server timeout.
> > > Verification status: NOT VERIFIED
> > > Last attempt Mar 28, 2008: We encountered an error looking up your
> > > site's domain name.
> > > If it's software it would be consistent. The DNS lookup code is
> > > simple and the Sofware Engineers will not find the problem.
> > > I say this because every delay is causing me money and I anticipate
> > > the SEs won't find it and we will be left out in the cold. Time is of
> > > the Essense!
> > > I realize there are many reasons via the posts for NOT VERIFIED caused
> > > by user or configuration errors, internet response times, server
> > > activity, etc., but in the end of this there will be a number of
> > > webmasters that will still have a consistent error and the fault will
> > > erroneously lie at our ISP..
> > > My suggestion for those left behind would be to find common ground;
> > > If it still persists we should setup a separate post and if we could
> > > establish the origination Google IP and path we go through we could
> > > isolate and identify where the problem may be.
> > > It's been my experience, we will have to tell them what the problem is
> > > before they will resolve it. You know the old finger pointing game and
> > > we suffer.
> > > FYI - my domain is headcoverleash,com
> > > If anyone knows the actual Google IP the webmaster host originates
> > > from we can trace the path and look for any common paths for those
> > > still experiencing the problem.
> > > On Mar 28, 7:04 pm, HCL wrote:
> > > > Thank $,
> > > > You know these problems could be caused by hardware/routers
> > > > malfunctions at Google or or on their path out.
> > > > After the software engineers say there is no problem, look to the
> > > > hardware. Check the router or link errors.
> > > > On Mar 28, 6:18 pm, $e0Guy wrote:
> > > > > Now that I think about it, I would have to agree with HCL in the
> > > > > possibility that other issues are arising as a result of this latest
> > > > > problem. We are getting intermittent "errors" in some of our sitemaps
> > > > > now that were perfectly fine previously.
> > > > > If Google's system thinks there are problems with our sitemap.xml file
> > > > > then the possiblity exists this will affect how Google processes and
> > > > > makes use of that sitemap.xml file
> > > > > One day it shows as no errors, next it shows 4 errors, the next it's
> > > > > fine, and no changes on our part.
> > > > > Again this is not the case with the majority of our sites, but for a
> > > > > few newer sites it is.
> > > > > On Mar 28, 6:11 pm, HCL wrote:
> > > > > > John,
> > > > > > I beg to differ. There is a major impact, not just showing
> > > > > > statistics. This error seems to have caused a delay for Google to
> > > > > > visit an index and update to a site. My site has not been updated
> > > > > > since 03/11 and I have made major changes that are not reflected in
> > > > > > search results. A side error to this is when a sitmape is updated,
> > > > > > Google stopped reindexing the site. My sitemap shows no URL's indexed
> > > > > > down from 10 to none.
> > > > > > I have stop showing in the number 1 position and all the way back to
> > > > > > 50 on a search that is term incusive of my domain name and previous
> > > > > > search terms..
> > > > > > My Google Base items no longer show in search product results or even
> > > > > > in the tools that I have base items in myr account menu.
> > > > > > I would say there are many relationships to this problem and hope you
> > > > > > will understand that is has serious implicattion and pursue these
> > > > > > relationships I've outline.
> > > > > > Many people saw this NOT VERIFIED problem.
> > > > > > One should be concerned that there seems to be no obvious way to
> > > > > > contact webmaster technical support to report a problem.
> > > > > > Maybe someone could show me how, but it's not obvious to me.
> > > > > > If others have experienced these similar implication, it would
> > > > > > demonstrate there are other problems created. Check your positions,
> > > > > > producs and results.
> > > > > > On Mar 27, 11:14 am, JohnMu wrote:
> > > > > > > Hi everyone!
> > > > > > > I just wanted to give a short heads-up that we're aware of the issue
> > > > > > > with site verification in Webmaster Tools. The team is working on it,
> > > > > > > so you should all be able to take a deeper look into your site's
> > > > > > > indexing through Webmaster Tools soon!
> > > > > > > If your site was unverified, it will generally have no impact on any
> > > > > > > settings or statistics in your account. They will all be back once
> > > > > > > your site is re-verified.
> > > > > > > I'm sorry for the disruption and hope to see you all in our chat
> > > > > > > tomorrow!
> > > > > > > John- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -
So I believe this was a Google error since my ISP (ipower) has yet to
make the changes you recommended.
I thank you for your technical expertise, but it appears Google has
taken some action and they should acknowledge this for us lonely
people to keep our sanity,
> Same Glue Looks like the A records (the GLUE) got from the parent zone
> check are different than the ones got from your nameservers. You have
> to make sure your parent server has the same NS records for your zone
> as you do.I detected some problems as follows:
> For ns1.ipowerdns.com the parent reported: ['66.96.142.103'] and your
> nameservers reported: ['66.96.142.102', '66.96.131.28']
> For ns1.ipowerweb.net the parent reported: ['66.96.142.103'] and your
> nameservers reported: ['66.96.131.116', '66.96.142.103']
> Missing nameservers reported by parent FAIL: The following nameservers
> are listed at your nameservers as nameservers for your domain, but are
> not listed at the parent nameservers (see RFC2181 5.4.1). You need to
> make sure that these nameservers are working.If they are not working
> ok, you may have problems!
> ns2.ipowerdns.com
> ns2.ipowerweb.net
> Either error is plausible with such a dns setup.
> Talk to your hoster to fix the dns.
> You also need to have all the correct namesevers in your domain
> registry - they have to agree with those provided by the hoster.
> On Mar 28, 11:16 pm, HCL wrote:
> > Here's a little more input for the powers to be:
> > My responses to try to verify varies:
> > Verification status: NOT VERIFIED
> > Last attempt Mar 28, 2008: We were unable to verify your file due to a
> > server timeout.
> > Verification status: NOT VERIFIED
> > Last attempt Mar 28, 2008: We encountered an error looking up your
> > site's domain name.
> > If it's software it would be consistent. The DNS lookup code is
> > simple and the Sofware Engineers will not find the problem.
> > I say this because every delay is causing me money and I anticipate
> > the SEs won't find it and we will be left out in the cold. Time is of
> > the Essense!
> > I realize there are many reasons via the posts for NOT VERIFIED caused
> > by user or configuration errors, internet response times, server
> > activity, etc., but in the end of this there will be a number of
> > webmasters that will still have a consistent error and the fault will
> > erroneously lie at our ISP..
> > My suggestion for those left behind would be to find common ground;
> > If it still persists we should setup a separate post and if we could
> > establish the origination Google IP and path we go through we could
> > isolate and identify where the problem may be.
> > It's been my experience, we will have to tell them what the problem is
> > before they will resolve it. You know the old finger pointing game and
> > we suffer.
> > FYI - my domain is headcoverleash,com
> > If anyone knows the actual Google IP the webmaster host originates
> > from we can trace the path and look for any common paths for those
> > still experiencing the problem.
> > On Mar 28, 7:04 pm, HCL wrote:
> > > Thank $,
> > > You know these problems could be caused by hardware/routers
> > > malfunctions at Google or or on their path out.
> > > Intermittent hardware problems will drive everyone crazy.
> > > After the software engineers say there is no problem, look to the
> > > hardware. Check the router or link errors.
> > > On Mar 28, 6:18 pm, $e0Guy wrote:
> > > > Now that I think about it, I would have to agree with HCL in the
> > > > possibility that other issues are arising as a result of this latest
> > > > problem. We are getting intermittent "errors" in some of our sitemaps
> > > > now that were perfectly fine previously.
> > > > If Google's system thinks there are problems with our sitemap.xml file
> > > > then the possiblity exists this will affect how Google processes and
> > > > makes use of that sitemap.xml file
> > > > One day it shows as no errors, next it shows 4 errors, the next it's
> > > > fine, and no changes on our part.
> > > > Again this is not the case with the majority of our sites, but for a
> > > > few newer sites it is.
> > > > On Mar 28, 6:11 pm, HCL wrote:
> > > > > John,
> > > > > I beg to differ. There is a major impact, not just showing
> > > > > statistics. This error seems to have caused a delay for Google to
> > > > > visit an index and update to a site. My site has not been updated
> > > > > since 03/11 and I have made major changes that are not reflected in
> > > > > search results. A side error to this is when a sitmape is updated,
> > > > > Google stopped reindexing the site. My sitemap shows no URL's indexed
> > > > > down from 10 to none.
> > > > > I have stop showing in the number 1 position and all the way back to
> > > > > 50 on a search that is term incusive of my domain name and previous
> > > > > search terms..
> > > > > My Google Base items no longer show in search product results or even
> > > > > in the tools that I have base items in myr account menu.
> > > > > I would say there are many relationships to this problem and hope you
> > > > > will understand that is has serious implicattion and pursue these
> > > > > relationships I've outline.
> > > > > Many people saw this NOT VERIFIED problem.
> > > > > One should be concerned that there seems to be no obvious way to
> > > > > contact webmaster technical support to report a problem.
> > > > > Maybe someone could show me how, but it's not obvious to me.
> > > > > If others have experienced these similar implication, it would
> > > > > demonstrate there are other problems created. Check your positions,
> > > > > producs and results.
> > > > > On Mar 27, 11:14 am, JohnMu wrote:
> > > > > > Hi everyone!
> > > > > > I just wanted to give a short heads-up that we're aware of the issue
> > > > > > with site verification in Webmaster Tools. The team is working on it,
> > > > > > so you should all be able to take a deeper look into your site's
> > > > > > indexing through Webmaster Tools soon!
> > > > > > If your site was unverified, it will generally have no impact on any
> > > > > > settings or statistics in your account. They will all be back once
> > > > > > your site is re-verified.
> > > > > > I'm sorry for the disruption and hope to see you all in our chat
> > > > > > tomorrow!
I just wanted to thank all the people who responded to this situation.
It proves to me again the value of exchanging our knowledge. We all
grow from each others experiences.
Can anyone put a value on this forum and the knowledge you gain from
participating? Just contribute in a constructive manner. I'm an old
computer buck and learn something new everyday. I really don't want to
know this stuff anymore, My brain is fried after 40+ years in the
computer industry, but when I need it, this is a great place. I just
rather be playing golf and playing with videos.
> So I believe this was a Google error since my ISP (ipower) has yet to
> make the changes you recommended.
> I thank you for your technical expertise, but it appears Google has
> taken some action and they should acknowledge this for us lonely
> people to keep our sanity,
> > Same Glue Looks like the A records (the GLUE) got from the parent zone
> > check are different than the ones got from your nameservers. You have
> > to make sure your parent server has the same NS records for your zone
> > as you do.I detected some problems as follows:
> > For ns1.ipowerdns.com the parent reported: ['66.96.142.103'] and your
> > nameservers reported: ['66.96.142.102', '66.96.131.28']
> > For ns1.ipowerweb.net the parent reported: ['66.96.142.103'] and your
> > nameservers reported: ['66.96.131.116', '66.96.142.103']
> > Missing nameservers reported by parent FAIL: The following nameservers
> > are listed at your nameservers as nameservers for your domain, but are
> > not listed at the parent nameservers (see RFC2181 5.4.1). You need to
> > make sure that these nameservers are working.If they are not working
> > ok, you may have problems!
> > ns2.ipowerdns.com
> > ns2.ipowerweb.net
> > Either error is plausible with such a dns setup.
> > Talk to your hoster to fix the dns.
> > You also need to have all the correct namesevers in your domain
> > registry - they have to agree with those provided by the hoster.
> > On Mar 28, 11:16 pm, HCL wrote:
> > > Here's a little more input for the powers to be:
> > > My responses to try to verify varies:
> > > Verification status: NOT VERIFIED
> > > Last attempt Mar 28, 2008: We were unable to verify your file due to a
> > > server timeout.
> > > Verification status: NOT VERIFIED
> > > Last attempt Mar 28, 2008: We encountered an error looking up your
> > > site's domain name.
> > > If it's software it would be consistent. The DNS lookup code is
> > > simple and the Sofware Engineers will not find the problem.
> > > I say this because every delay is causing me money and I anticipate
> > > the SEs won't find it and we will be left out in the cold. Time is of
> > > the Essense!
> > > I realize there are many reasons via the posts for NOT VERIFIED caused
> > > by user or configuration errors, internet response times, server
> > > activity, etc., but in the end of this there will be a number of
> > > webmasters that will still have a consistent error and the fault will
> > > erroneously lie at our ISP..
> > > My suggestion for those left behind would be to find common ground;
> > > If it still persists we should setup a separate post and if we could
> > > establish the origination Google IP and path we go through we could
> > > isolate and identify where the problem may be.
> > > It's been my experience, we will have to tell them what the problem is
> > > before they will resolve it. You know the old finger pointing game and
> > > we suffer.
> > > FYI - my domain is headcoverleash,com
> > > If anyone knows the actual Google IP the webmaster host originates
> > > from we can trace the path and look for any common paths for those
> > > still experiencing the problem.
> > > On Mar 28, 7:04 pm, HCL wrote:
> > > > Thank $,
> > > > You know these problems could be caused by hardware/routers
> > > > malfunctions at Google or or on their path out.
> > > > After the software engineers say there is no problem, look to the
> > > > hardware. Check the router or link errors.
> > > > On Mar 28, 6:18 pm, $e0Guy wrote:
> > > > > Now that I think about it, I would have to agree with HCL in the
> > > > > possibility that other issues are arising as a result of this latest
> > > > > problem. We are getting intermittent "errors" in some of our sitemaps
> > > > > now that were perfectly fine previously.
> > > > > If Google's system thinks there are problems with our sitemap.xml file
> > > > > then the possiblity exists this will affect how Google processes and
> > > > > makes use of that sitemap.xml file
> > > > > One day it shows as no errors, next it shows 4 errors, the next it's
> > > > > fine, and no changes on our part.
> > > > > Again this is not the case with the majority of our sites, but for a
> > > > > few newer sites it is.
> > > > > On Mar 28, 6:11 pm, HCL wrote:
> > > > > > John,
> > > > > > I beg to differ. There is a major impact, not just showing
> > > > > > statistics. This error seems to have caused a delay for Google to
> > > > > > visit an index and update to a site. My site has not been updated
> > > > > > since 03/11 and I have made major changes that are not reflected in
> > > > > > search results. A side error to this is when a sitmape is updated,
> > > > > > Google stopped reindexing the site. My sitemap shows no URL's indexed
> > > > > > down from 10 to none.
> > > > > > I have stop showing in the number 1 position and all the way back to
> > > > > > 50 on a search that is term incusive of my domain name and previous
> > > > > > search terms..
> > > > > > My Google Base items no longer show in search product results or even
> > > > > > in the tools that I have base items in myr account menu.
> > > > > > I would say there are many relationships to this problem and hope you
> > > > > > will understand that is has serious implicattion and pursue these
> > > > > > relationships I've outline.
> > > > > > Many people saw this NOT VERIFIED problem.
> > > > > > One should be concerned that there seems to be no obvious way to
> > > > > > contact webmaster technical support to report a problem.
> > > > > > Maybe someone could show me how, but it's not obvious to me.
> > > > > > If others have experienced these similar implication, it would
> > > > > > demonstrate there are other problems created. Check your positions,
> > > > > > producs and results.
> > > > > > On Mar 27, 11:14 am, JohnMu wrote:
> > > > > > > Hi everyone!
> > > > > > > I just wanted to give a short heads-up that we're aware of the issue
> > > > > > > with site verification in Webmaster Tools. The team is working on it,
> > > > > > > so you should all be able to take a deeper look into your site's
> > > > > > > indexing through Webmaster Tools soon!
> > > > > > > If your site was unverified, it will generally have no impact on any
> > > > > > > settings or statistics in your account. They will all be back once
> > > > > > > your site is re-verified.
> > > > > > > I'm sorry for the disruption and hope to see you all in our chat
> > > > > > > tomorrow!
> > > > > > > John- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -
> So I believe this was a Google error since my ISP (ipower) has yet to
> make the changes you recommended.
> I thank you for your technical expertise, but it appears Google has
> taken some action and they should acknowledge this for us lonely
> people to keep our sanity,
> > Same Glue Looks like the A records (the GLUE) got from the parent zone
> > check are different than the ones got from your nameservers. You have
> > to make sure your parent server has the same NS records for your zone
> > as you do.I detected some problems as follows:
> > For ns1.ipowerdns.com the parent reported: ['66.96.142.103'] and your
> > nameservers reported: ['66.96.142.102', '66.96.131.28']
> > For ns1.ipowerweb.net the parent reported: ['66.96.142.103'] and your
> > nameservers reported: ['66.96.131.116', '66.96.142.103']
> > Missing nameservers reported by parent FAIL: The following nameservers
> > are listed at your nameservers as nameservers for your domain, but are
> > not listed at the parent nameservers (see RFC2181 5.4.1). You need to
> > make sure that these nameservers are working.If they are not working
> > ok, you may have problems!
> > ns2.ipowerdns.com
> > ns2.ipowerweb.net
> > Either error is plausible with such a dns setup.
> > Talk to your hoster to fix the dns.
> > You also need to have all the correct namesevers in your domain
> > registry - they have to agree with those provided by the hoster.
> > On Mar 28, 11:16 pm, HCL wrote:
> > > Here's a little more input for the powers to be:
> > > My responses to try to verify varies:
> > > Verification status: NOT VERIFIED
> > > Last attempt Mar 28, 2008: We were unable to verify your file due to a
> > > server timeout.
> > > Verification status: NOT VERIFIED
> > > Last attempt Mar 28, 2008: We encountered an error looking up your
> > > site's domain name.
> > > If it's software it would be consistent. The DNS lookup code is
> > > simple and the Sofware Engineers will not find the problem.
> > > I say this because every delay is causing me money and I anticipate
> > > the SEs won't find it and we will be left out in the cold. Time is of
> > > the Essense!
> > > I realize there are many reasons via the posts for NOT VERIFIED caused
> > > by user or configuration errors, internet response times, server
> > > activity, etc., but in the end of this there will be a number of
> > > webmasters that will still have a consistent error and the fault will
> > > erroneously lie at our ISP..
> > > My suggestion for those left behind would be to find common ground;
> > > If it still persists we should setup a separate post and if we could
> > > establish the origination Google IP and path we go through we could
> > > isolate and identify where the problem may be.
> > > It's been my experience, we will have to tell them what the problem is
> > > before they will resolve it. You know the old finger pointing game and
> > > we suffer.
> > > FYI - my domain is headcoverleash,com
> > > If anyone knows the actual Google IP the webmaster host originates
> > > from we can trace the path and look for any common paths for those
> > > still experiencing the problem.
> > > On Mar 28, 7:04 pm, HCL wrote:
> > > > Thank $,
> > > > You know these problems could be caused by hardware/routers
> > > > malfunctions at Google or or on their path out.
> > > > After the software engineers say there is no problem, look to the
> > > > hardware. Check the router or link errors.
> > > > On Mar 28, 6:18 pm, $e0Guy wrote:
> > > > > Now that I think about it, I would have to agree with HCL in the
> > > > > possibility that other issues are arising as a result of this latest
> > > > > problem. We are getting intermittent "errors" in some of our sitemaps
> > > > > now that were perfectly fine previously.
> > > > > If Google's system thinks there are problems with our sitemap.xml file
> > > > > then the possiblity exists this will affect how Google processes and
> > > > > makes use of that sitemap.xml file
> > > > > One day it shows as no errors, next it shows 4 errors, the next it's
> > > > > fine, and no changes on our part.
> > > > > Again this is not the case with the majority of our sites, but for a
> > > > > few newer sites it is.
> > > > > On Mar 28, 6:11 pm, HCL wrote:
> > > > > > John,
> > > > > > I beg to differ. There is a major impact, not just showing
> > > > > > statistics. This error seems to have caused a delay for Google to
> > > > > > visit an index and update to a site. My site has not been updated
> > > > > > since 03/11 and I have made major changes that are not reflected in
> > > > > > search results. A side error to this is when a sitmape is updated,
> > > > > > Google stopped reindexing the site. My sitemap shows no URL's indexed
> > > > > > down from 10 to none.
> > > > > > I have stop showing in the number 1 position and all the way back to
> > > > > > 50 on a search that is term incusive of my domain name and previous
> > > > > > search terms..
> > > > > > My Google Base items no longer show in search product results or even
> > > > > > in the tools that I have base items in myr account menu.
> > > > > > I would say there are many relationships to this problem and hope you
> > > > > > will understand that is has serious implicattion and pursue these
> > > > > > relationships I've outline.
> > > > > > Many people saw this NOT VERIFIED problem.
> > > > > > One should be concerned that there seems to be no obvious way to
> > > > > > contact webmaster technical support to report a problem.
> > > > > > Maybe someone could show me how, but it's not obvious to me.
> > > > > > If others have experienced these similar implication, it would
> > > > > > demonstrate there are other problems created. Check your positions,
> > > > > > producs and results.
> > > > > > On Mar 27, 11:14 am, JohnMu wrote:
> > > > > > > Hi everyone!
> > > > > > > I just wanted to give a short heads-up that we're aware of the issue
> > > > > > > with site verification in Webmaster Tools. The team is working on it,
> > > > > > > so you should all be able to take a deeper look into your site's
> > > > > > > indexing through Webmaster Tools soon!
> > > > > > > If your site was unverified, it will generally have no impact on any
> > > > > > > settings or statistics in your account. They will all be back once
> > > > > > > your site is re-verified.
> > > > > > > I'm sorry for the disruption and hope to see you all in our chat
> > > > > > > tomorrow!
> > > > > > > John- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -
> > > > Recursive Queries I could use the nameservers listed below to performe
> > > > recursive queries. It may be that I am wrong but the chances of that
> > > > are low. You should not have nameservers that allow recursive queries
> > > > as this will allow almost anyone to use your nameservers and can cause
> > > > problems. Problem record(s) are:
> > > > 71.18.216.3
> > > > 71.18.255.99
> > > > On Mar 28, 3:59 pm, Maria3a wrote:
> > > > > Hi John,
> > > > > I gather I'm having the same problem too.. Everything was fine
> > > > > yesterday, but today I get the message that the site/domain cannot be
> > > > > verified..
> > > > > domain is:
> > > > > glanmore.org
> > > > > re: verification issues - and I've added the verification meta tag
> > > > > in.. 3 times :-) but it still won't verify. I did the html
> > > > > verfication page as well - it didn't work.. (I've deleted it since).
> > > > > I ended up calling my webhost (before I came here to this blog) and
> > > > > they say all the servers are correct.. for both domains I have, i.e.,
> > > > > I have another domain hosted by the same company, same DNS servers,
> > > > > and it is fine re: verification at:
> > > > > torchysland.com
> > > > > so, I'm no techie.. and really don't know what to do..
> > > > > On Mar 27, 11:14 am, JohnMu wrote:
> > > > > > Hi everyone!
> > > > > > I just wanted to give a short heads-up that we're aware of the issue
> > > > > > with site verification in Webmaster Tools. The team is working on it,
> > > > > > so you should all be able to take a deeper look into your site's
> > > > > > indexing through Webmaster Tools soon!
> > > > > > If your site was unverified, it will generally have no impact on any
> > > > > > settings or statistics in your account. They will all be back once
> > > > > > your site is re-verified.
> > > > > > I'm sorry for the disruption and hope to see you all in our chat
> > > > > > tomorrow!
> > > > > > John- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -
> > So I believe this was a Google error since my ISP (ipower) has yet to
> > make the changes you recommended.
> > I thank you for your technical expertise, but it appears Google has
> > taken some action and they should acknowledge this for us lonely
> > people to keep our sanity,
> > > Same Glue Looks like the A records (the GLUE) got from the parent zone
> > > check are different than the ones got from your nameservers. You have
> > > to make sure your parent server has the same NS records for your zone
> > > as you do.I detected some problems as follows:
> > > For ns1.ipowerdns.com the parent reported: ['66.96.142.103'] and your
> > > nameservers reported: ['66.96.142.102', '66.96.131.28']
> > > For ns1.ipowerweb.net the parent reported: ['66.96.142.103'] and your
> > > nameservers reported: ['66.96.131.116', '66.96.142.103']
> > > Missing nameservers reported by parent FAIL: The following nameservers
> > > are listed at your nameservers as nameservers for your domain, but are
> > > not listed at the parent nameservers (see RFC2181 5.4.1). You need to
> > > make sure that these nameservers are working.If they are not working
> > > ok, you may have problems!
> > > ns2.ipowerdns.com
> > > ns2.ipowerweb.net
> > > Either error is plausible with such a dns setup.
> > > Talk to your hoster to fix the dns.
> > > You also need to have all the correct namesevers in your domain
> > > registry - they have to agree with those provided by the hoster.
> > > On Mar 28, 11:16 pm, HCL wrote:
> > > > Here's a little more input for the powers to be:
> > > > My responses to try to verify varies:
> > > > Verification status: NOT VERIFIED
> > > > Last attempt Mar 28, 2008: We were unable to verify your file due to a
> > > > server timeout.
> > > > Verification status: NOT VERIFIED
> > > > Last attempt Mar 28, 2008: We encountered an error looking up your
> > > > site's domain name.
> > > > If it's software it would be consistent. The DNS lookup code is
> > > > simple and the Sofware Engineers will not find the problem.
> > > > I say this because every delay is causing me money and I anticipate
> > > > the SEs won't find it and we will be left out in the cold. Time is of
> > > > the Essense!
> > > > I realize there are many reasons via the posts for NOT VERIFIED caused
> > > > by user or configuration errors, internet response times, server
> > > > activity, etc., but in the end of this there will be a number of
> > > > webmasters that will still have a consistent error and the fault will
> > > > erroneously lie at our ISP..
> > > > My suggestion for those left behind would be to find common ground;
> > > > If it still persists we should setup a separate post and if we could
> > > > establish the origination Google IP and path we go through we could
> > > > isolate and identify where the problem may be.
> > > > It's been my experience, we will have to tell them what the problem is
> > > > before they will resolve it. You know the old finger pointing game and
> > > > we suffer.
> > > > FYI - my domain is headcoverleash,com
> > > > If anyone knows the actual Google IP the webmaster host originates
> > > > from we can trace the path and look for any common paths for those
> > > > still experiencing the problem.
> > > > On Mar 28, 7:04 pm, HCL wrote:
> > > > > Thank $,
> > > > > You know these problems could be caused by hardware/routers
> > > > > malfunctions at Google or or on their path out.
> > > > > After the software engineers say there is no problem, look to the
> > > > > hardware. Check the router or link errors.
> > > > > On Mar 28, 6:18 pm, $e0Guy wrote:
> > > > > > Now that I think about it, I would have to agree with HCL in the
> > > > > > possibility that other issues are arising as a result of this latest
> > > > > > problem. We are getting intermittent "errors" in some of our sitemaps
> > > > > > now that were perfectly fine previously.
> > > > > > If Google's system thinks there are problems with our sitemap.xml file
> > > > > > then the possiblity exists this will affect how Google processes and
> > > > > > makes use of that sitemap.xml file
> > > > > > One day it shows as no errors, next it shows 4 errors, the next it's
> > > > > > fine, and no changes on our part.
> > > > > > Again this is not the case with the majority of our sites, but for a
> > > > > > few newer sites it is.
> > > > > > On Mar 28, 6:11 pm, HCL wrote:
> > > > > > > John,
> > > > > > > I beg to differ. There is a major impact, not just showing
> > > > > > > statistics. This error seems to have caused a delay for Google to
> > > > > > > visit an index and update to a site. My site has not been updated
> > > > > > > since 03/11 and I have made major changes that are not reflected in
> > > > > > > search results. A side error to this is when a sitmape is updated,
> > > > > > > Google stopped reindexing the site. My sitemap shows no URL's indexed
> > > > > > > down from 10 to none.
> > > > > > > I have stop showing in the number 1 position and all the way back to
> > > > > > > 50 on a search that is term incusive of my domain name and previous
> > > > > > > search terms..
> > > > > > > My Google Base items no longer show in search product results or even
> > > > > > > in the tools that I have base items in myr account menu.
> > > > > > > I would say there are many relationships to this problem and hope you
> > > > > > > will understand that is has serious implicattion and pursue these
> > > > > > > relationships I've outline.
> > > > > > > Many people saw this NOT VERIFIED problem.
> > > > > > > One should be concerned that there seems to be no obvious way to
> > > > > > > contact webmaster technical support to report a problem.
> > > > > > > Maybe someone could show me how, but it's not obvious to me.
> > > > > > > If others have experienced these similar implication, it would
> > > > > > > demonstrate there are other problems created. Check your positions,
> > > > > > > producs and results.
> > > > > > > On Mar 27, 11:14 am, JohnMu wrote:
> > > > > > > > Hi everyone!
> > > > > > > > I just wanted to give a short heads-up that we're aware of the issue
> > > > > > > > with site verification in Webmaster Tools. The team is working on it,
> > > > > > > > so you should all be able to take a deeper look into your site's
> > > > > > > > indexing through Webmaster Tools soon!
> > > > > > > > If your site was unverified, it will generally have no impact on any
> > > > > > > > settings or statistics in your account. They will all be back once
> > > > > > > > your site is re-verified.
> > > > > > > > I'm sorry for the disruption and hope to see you all in our chat
> > > > > > > > tomorrow!
> > > > > > > > John- Hide quoted text -
> > > > > > - Show quoted text -- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -
> > > So I believe this was a Google error since my ISP (ipower) has yet to
> > > make the changes you recommended.
> > > I thank you for your technical expertise, but it appears Google has
> > > taken some action and they should acknowledge this for us lonely
> > > people to keep our sanity,
> > > > Same Glue Looks like the A records (the GLUE) got from the parent zone
> > > > check are different than the ones got from your nameservers. You have
> > > > to make sure your parent server has the same NS records for your zone
> > > > as you do.I detected some problems as follows:
> > > > For ns1.ipowerdns.com the parent reported: ['66.96.142.103'] and your
> > > > nameservers reported: ['66.96.142.102', '66.96.131.28']
> > > > For ns1.ipowerweb.net the parent reported: ['66.96.142.103'] and your
> > > > nameservers reported: ['66.96.131.116', '66.96.142.103']
> > > > Missing nameservers reported by parent FAIL: The following nameservers
> > > > are listed at your nameservers as nameservers for your domain, but are
> > > > not listed at the parent nameservers (see RFC2181 5.4.1). You need to
> > > > make sure that these nameservers are working.If they are not working
> > > > ok, you may have problems!
> > > > ns2.ipowerdns.com
> > > > ns2.ipowerweb.net
> > > > Either error is plausible with such a dns setup.
> > > > Talk to your hoster to fix the dns.
> > > > You also need to have all the correct namesevers in your domain
> > > > registry - they have to agree with those provided by the hoster.
> > > > On Mar 28, 11:16 pm, HCL wrote:
> > > > > Here's a little more input for the powers to be:
> > > > > My responses to try to verify varies:
> > > > > Verification status: NOT VERIFIED
> > > > > Last attempt Mar 28, 2008: We were unable to verify your file due to a
> > > > > server timeout.
> > > > > Verification status: NOT VERIFIED
> > > > > Last attempt Mar 28, 2008: We encountered an error looking up your
> > > > > site's domain name.
> > > > > If it's software it would be consistent. The DNS lookup code is
> > > > > simple and the Sofware Engineers will not find the problem.
> > > > > I say this because every delay is causing me money and I anticipate
> > > > > the SEs won't find it and we will be left out in the cold. Time is of
> > > > > the Essense!
> > > > > I realize there are many reasons via the posts for NOT VERIFIED caused
> > > > > by user or configuration errors, internet response times, server
> > > > > activity, etc., but in the end of this there will be a number of
> > > > > webmasters that will still have a consistent error and the fault will
> > > > > erroneously lie at our ISP..
> > > > > My suggestion for those left behind would be to find common ground;
> > > > > If it still persists we should setup a separate post and if we could
> > > > > establish the origination Google IP and path we go through we could
> > > > > isolate and identify where the problem may be.
> > > > > It's been my experience, we will have to tell them what the problem is
> > > > > before they will resolve it. You know the old finger pointing game and
> > > > > we suffer.
> > > > > FYI - my domain is headcoverleash,com
> > > > > If anyone knows the actual Google IP the webmaster host originates
> > > > > from we can trace the path and look for any common paths for those
> > > > > still experiencing the problem.
> > > > > On Mar 28, 7:04 pm, HCL wrote:
> > > > > > Thank $,
> > > > > > You know these problems could be caused by hardware/routers
> > > > > > malfunctions at Google or or on their path out.
> > > > > > After the software engineers say there is no problem, look to the
> > > > > > hardware. Check the router or link errors.
> > > > > > On Mar 28, 6:18 pm, $e0Guy wrote:
> > > > > > > Now that I think about it, I would have to agree with HCL in the
> > > > > > > possibility that other issues are arising as a result of this latest
> > > > > > > problem. We are getting intermittent "errors" in some of our sitemaps
> > > > > > > now that were perfectly fine previously.
> > > > > > > If Google's system thinks there are problems with our sitemap.xml file
> > > > > > > then the possiblity exists this will affect how Google processes and
> > > > > > > makes use of that sitemap.xml file
> > > > > > > One day it shows as no errors, next it shows 4 errors, the next it's
> > > > > > > fine, and no changes on our part.
> > > > > > > Again this is not the case with the majority of our sites, but for a
> > > > > > > few newer sites it is.
> > > > > > > On Mar 28, 6:11 pm, HCL wrote:
> > > > > > > > John,
> > > > > > > > I beg to differ. There is a major impact, not just showing
> > > > > > > > statistics. This error seems to have caused a delay for Google to
> > > > > > > > visit an index and update to a site. My site has not been updated
> > > > > > > > since 03/11 and I have made major changes that are not reflected in
> > > > > > > > search results. A side error to this is when a sitmape is updated,
> > > > > > > > Google stopped reindexing the site. My sitemap shows no URL's indexed
> > > > > > > > down from 10 to none.
> > > > > > > > I have stop showing in the number 1 position and all the way back to
> > > > > > > > 50 on a search that is term incusive of my domain name and previous
> > > > > > > > search terms..
> > > > > > > > My Google Base items no longer show in search product results or even
> > > > > > > > in the tools that I have base items in myr account menu.
> > > > > > > > I would say there are many relationships to this problem and hope you
> > > > > > > > will understand that is has serious implicattion and pursue these
> > > > > > > > relationships I've outline.
> > > > > > > > Many people saw this NOT VERIFIED problem.
> > > > > > > > One should be concerned that there seems to be no obvious way to
> > > > > > > > contact webmaster technical support to report a problem.
> > > > > > > > Maybe someone could show me how, but it's not obvious to me.
> > > > > > > > If others have experienced these similar implication, it would
> > > > > > > > demonstrate there are other problems created. Check your positions,
> > > > > > > > producs and results.
> > > > > > > > On Mar 27, 11:14 am, JohnMu wrote:
> > > > > > > > > Hi everyone!
> > > > > > > > > I just wanted to give a short heads-up that we're aware of the issue
> > > > > > > > > with site verification in Webmaster Tools. The team is working on it,
> > > > > > > > > so you should all be able to take a deeper look into your site's
> > > > > > > > > indexing through Webmaster Tools soon!
> > > > > > > > > If your site was unverified, it will generally have no impact on any
> > > > > > > > > settings or statistics in your account. They will all be back once
> > > > > > > > > your site is re-verified.
> > > > > > > > > I'm sorry for the disruption and hope to see you all in our chat
> > > > > > > > > tomorrow!
> > > > > > > > > John- Hide quoted text -
> > > > > > > - Show quoted text -- Hide quoted text -
> > > > > > - Show quoted text -- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -
> > > > So I believe this was a Google error since my ISP (ipower) has yet to
> > > > make the changes you recommended.
> > > > I thank you for your technical expertise, but it appears Google has
> > > > taken some action and they should acknowledge this for us lonely
> > > > people to keep our sanity,
> > > > > Same Glue Looks like the A records (the GLUE) got from the parent zone
> > > > > check are different than the ones got from your nameservers. You have
> > > > > to make sure your parent server has the same NS records for your zone
> > > > > as you do.I detected some problems as follows:
> > > > > For ns1.ipowerdns.com the parent reported: ['66.96.142.103'] and your
> > > > > nameservers reported: ['66.96.142.102', '66.96.131.28']
> > > > > For ns1.ipowerweb.net the parent reported: ['66.96.142.103'] and your
> > > > > nameservers reported: ['66.96.131.116', '66.96.142.103']
> > > > > Missing nameservers reported by parent FAIL: The following nameservers
> > > > > are listed at your nameservers as nameservers for your domain, but are
> > > > > not listed at the parent nameservers (see RFC2181 5.4.1). You need to
> > > > > make sure that these nameservers are working.If they are not working
> > > > > ok, you may have problems!
> > > > > ns2.ipowerdns.com
> > > > > ns2.ipowerweb.net
> > > > > Either error is plausible with such a dns setup.
> > > > > Talk to your hoster to fix the dns.
> > > > > You also need to have all the correct namesevers in your domain
> > > > > registry - they have to agree with those provided by the hoster.
> > > > > On Mar 28, 11:16 pm, HCL wrote:
> > > > > > Here's a little more input for the powers to be:
> > > > > > My responses to try to verify varies:
> > > > > > Verification status: NOT VERIFIED
> > > > > > Last attempt Mar 28, 2008: We were unable to verify your file due to a
> > > > > > server timeout.
> > > > > > Verification status: NOT VERIFIED
> > > > > > Last attempt Mar 28, 2008: We encountered an error looking up your
> > > > > > site's domain name.
> > > > > > If it's software it would be consistent. The DNS lookup code is
> > > > > > simple and the Sofware Engineers will not find the problem.
> > > > > > I say this because every delay is causing me money and I anticipate
> > > > > > the SEs won't find it and we will be left out in the cold. Time is of
> > > > > > the Essense!
> > > > > > I realize there are many reasons via the posts for NOT VERIFIED caused
> > > > > > by user or configuration errors, internet response times, server
> > > > > > activity, etc., but in the end of this there will be a number of
> > > > > > webmasters that will still have a consistent error and the fault will
> > > > > > erroneously lie at our ISP..
> > > > > > My suggestion for those left behind would be to find common ground;
> > > > > > If it still persists we should setup a separate post and if we could
> > > > > > establish the origination Google IP and path we go through we could
> > > > > > isolate and identify where the problem may be.
> > > > > > It's been my experience, we will have to tell them what the problem is
> > > > > > before they will resolve it. You know the old finger pointing game and
> > > > > > we suffer.
> > > > > > FYI - my domain is headcoverleash,com
> > > > > > If anyone knows the actual Google IP the webmaster host originates
> > > > > > from we can trace the path and look for any common paths for those
> > > > > > still experiencing the problem.
> > > > > > On Mar 28, 7:04 pm, HCL wrote:
> > > > > > > Thank $,
> > > > > > > You know these problems could be caused by hardware/routers
> > > > > > > malfunctions at Google or or on their path out.
> > > > > > > After the software engineers say there is no problem, look to the
> > > > > > > hardware. Check the router or link errors.
> > > > > > > On Mar 28, 6:18 pm, $e0Guy wrote:
> > > > > > > > Now that I think about it, I would have to agree with HCL in the
> > > > > > > > possibility that other issues are arising as a result of this latest
> > > > > > > > problem. We are getting intermittent "errors" in some of our sitemaps
> > > > > > > > now that were perfectly fine previously.
> > > > > > > > If Google's system thinks there are problems with our sitemap.xml file
> > > > > > > > then the possiblity exists this will affect how Google processes and
> > > > > > > > makes use of that sitemap.xml file
> > > > > > > > One day it shows as no errors, next it shows 4 errors, the next it's
> > > > > > > > fine, and no changes on our part.
> > > > > > > > Again this is not the case with the majority of our sites, but for a
> > > > > > > > few newer sites it is.
> > > > > > > > On Mar 28, 6:11 pm, HCL wrote:
> > > > > > > > > John,
> > > > > > > > > I beg to differ. There is a major impact, not just showing
> > > > > > > > > statistics. This error seems to have caused a delay for Google to
> > > > > > > > > visit an index and update to a site. My site has not been updated
> > > > > > > > > since 03/11 and I have made major changes that are not reflected in
> > > > > > > > > search results. A side error to this is when a sitmape is updated,
> > > > > > > > > Google stopped reindexing the site. My sitemap shows no URL's indexed
> > > > > > > > > down from 10 to none.
> > > > > > > > > I have stop showing in the number 1 position and all the way back to
> > > > > > > > > 50 on a search that is term incusive of my domain name and previous
> > > > > > > > > search terms..
> > > > > > > > > My Google Base items no longer show in search product results or even
> > > > > > > > > in the tools that I have base items in myr account menu.
> > > > > > > > > I would say there are many relationships to this problem and hope you
> > > > > > > > > will understand that is has serious implicattion and pursue these
> > > > > > > > > relationships I've outline.
> > > > > > > > > Many people saw this NOT VERIFIED problem.
> > > > > > > > > One should be concerned that there seems to be no obvious way to
> > > > > > > > > contact webmaster technical support to report a problem.
> > > > > > > > > Maybe someone could show me how, but it's not obvious to me.
> > > > > > > > > If others have experienced these similar implication, it would
> > > > > > > > > demonstrate there are other problems created. Check your positions,
> > > > > > > > > producs and results.
> > > > > > > > > On Mar 27, 11:14 am, JohnMu wrote:
> > > > > > > > > > Hi everyone!
> > > > > > > > > > I just wanted to give a short heads-up that we're aware of the issue
> > > > > > > > > > with site verification in Webmaster Tools. The team is working on it,
> > > > > > > > > > so you should all be able to take a deeper look into your site's
> > > > > > > > > > indexing through Webmaster Tools soon!
> > > > > > > > > > If your site was unverified, it will generally have no impact on any
> > > > > > > > > > settings or statistics in your account. They will all be back once
> > > > > > > > > > your site is re-verified.
> > > > > > > > > > I'm sorry for the disruption and hope to see you all in our chat
> > > > > > > > > > tomorrow!
> > > > > > > > > > John- Hide quoted text -
> > > > > > > > - Show quoted text -- Hide quoted text -
> > > > > > > - Show quoted text -- Hide quoted text -
> > > > > > - Show quoted text -- Hide quoted text -
> > > > > - Show quoted text -- Hide quoted text -
I noticed that your 404 page is redirecting to /404.html, which is
returning a result code 200. You will have to fix that (make sure that
it returns 404) before you are able to verify.
> I noticed that your 404 page is redirecting to /404.html, which is
> returning a result code 200. You will have to fix that (make sure that
> it returns 404) before you are able to verify.
thanks. Now the verification goes through. But what I was stumped by
is Google was returning an error message which was not really related
to this cause.
Maybe google should throw an appropriate error message.
-aditya
Yep, just set up a new site today and I'm experiencing problems. I've
tried meta tags and the .html file. This site is set up on a free host
for the moment, I've had sites instantly verified before using this
host so I don't see what the problem is.
> Yep, just set up a new site today and I'm experiencing problems. I've
> tried meta tags and the .html file. This site is set up on a free host
> for the moment, I've had sites instantly verified before using this
> host so I don't see what the problem is.
> From what I can see it looks like this issue has been resolved. Thank
> you for your patience!
> If you still have problems with regards to verification, please
> continue to let us know.
> Thanks!
> John
Personal matters have meant I haven't been able to follow up until now
but I am one still having verification problems and I believe that my
DNS and server settings are fine. The problem first appeared in early
March, cleared for a couple of days, and then returned with no respite
since. I first posted on
http://groups.google.com/group/Google_Webmaster_Help-Tools/browse_thr... and webado kindly pointed out some minor robots.txt errors that I
fixed and also pointed me towards a tool that I wasn't aware of at web-
sniffer.net . I've used that repeatedly and have yet to see any server
timeouts over about 6 weeks. She had also mentioned the www.intodns.com tool (which was handy as I'd been looking for a replacement for
dnsstuff.com for a while).
While intodns showed some apparent errors I discussed it with my
hosting company (who have a good personal response on support issues)
and they told me that a number of the "errors" were due to the tool's
out of date analysis and they were 100% confident that their setup was
correct.
My sites all respond correctly to error requests and there are no
redirects in operation. From the logs I know that Googlebot visits
them regularly. Both verification methods have been tried on a number
of the sites to no effect. Error message alternates between server
timeout and domain name.
Could you have a look and tell me if there is an issue I can do
anything about or if the problem is at your end.
The addresses are:
I'm looking after a number of web sites one of which is http://www.contedavies.com.
All of our sites are no longer verifying. I have checked that the 404
error code is returned for a non-existant file and I have also checked
that the verification file exists and that the meta verification tag
is in the index page. But I am still stuck. I have also checked my
DNS using DNS Report and intoDNS both of which give the site a clean
bill of health. This was all working (roughly six weeks ago) and many
of our sites have been verified and left without being changed. All
sites were listed as needing to be verified at the same time. All web
sites are hosted on the same dedicated server although we have changed
nothing on he server in this time apart from adding web sites and
their respecitive DNS. I have not changed the DNS for existing sites.
I am really at a dead end with this and any help or ideas would be
greatfully accepted.
> > From what I can see it looks like this issue has been resolved. Thank
> > you for your patience!
> > If you still have problems with regards to verification, please
> > continue to let us know.
> > Thanks!
> > John
> Personal matters have meant I haven't been able to follow up until now
> but I am one still having verification problems and I believe that my
> DNS and server settings are fine. The problem first appeared in early
> March, cleared for a couple of days, and then returned with no respite
> since. I first posted onhttp://groups.google.com/group/Google_Webmaster_Help-Tools/browse_thr...
> and webado kindly pointed out some minor robots.txt errors that I
> fixed and also pointed me towards a tool that I wasn't aware of at web-
> sniffer.net . I've used that repeatedly and have yet to see any server
> timeouts over about 6 weeks. She had also mentioned thewww.intodns.com > tool (which was handy as I'd been looking for a replacement for
> dnsstuff.com for a while).
> While intodns showed some apparent errors I discussed it with my
> hosting company (who have a good personal response on support issues)
> and they told me that a number of the "errors" were due to the tool's
> out of date analysis and they were 100% confident that their setup was
> correct.
> My sites all respond correctly to error requests and there are no
> redirects in operation. From the logs I know that Googlebot visits
> them regularly. Both verification methods have been tried on a number
> of the sites to no effect. Error message alternates between server
> timeout and domain name.
> Could you have a look and tell me if there is an issue I can do
> anything about or if the problem is at your end.
> The addresses are:
