> Thank you,
> 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.
> Thanks again,
> Walt
> On Mar 28, 8:44 pm, webado wrote:
> > HCL, your dns zone has got problems:
> >http://www.intodns.com/headcoverleash.com
> > 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!
> > > > > > > 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 -
> - Show quoted text -
