Google OOPS Error

[jamison]

Recently several of our hosting clients are getting the Google OOPS error when accessing their hosted web site. It appears this is a recent Google problem. Any ideas on how we can help our clients resolve this issue.
Jim

[Matt]

Do you have a screen shot of the page and address bar?

[jamison]

The client didn't send one. We did have him change the name servers to the root name server and the problem went away. I have no idea why that would resolve the issue as the inability to access the web site was only on a few computers. For example, we could always access it with no problem. I was jus twondering if anyone else had experienced the problem and had found any fixes.

[Matt]

If you have time, care to elaborate on what "root nameservers" mean in this case?

Are you taliking about you set his local DNS to the world root nameservers, or private nameservers for your account?

[jamison]

I am talking about the local DNS to the world root name servers that actually provide the server number NS1.(and NS2)gendns(number).com. We changed to that from the private name servers.

[Matt]

If I understand correctly. That's a bad idea I guess. Well, maybe not so much anymore.

But world root are very overloaded and only update as fast as they can. Can you imagine .com root? Those machines are supposed to know every .com on the planet. That is why DNS resolution used to take 24-48 hours. They are better able to deal with root lookups now, but, it is still better to use local NS.

If root has the correct data, that is good, but maybe your local zone files are bad?

Or did I understand you are using our root? The generic DNS nameservers? (gendns)

Using gendns is a good alternative to world root NS. So, if you are using gendns and your private NS dont work, we should look at your zone file for your private nameserver.

Does your zone for your ns1/ns2 show, ns1 and ns2?

Does it show A records for ns1/ns2 that map to an IP?

If yes, can you ping those IP?

Lets start here.

[jamison]

Matt,
Thanks for your interest. The problem is resolved. The excellent Glowhost technical support folks turned us on to the gendns fix. The client can now reach the web site. We could always reach the site form our offices.
I put this in the forum simply to see if there were any other fixes to what is most likely a Google issue. Recently, a lot of folks seem to be running into this.
While I am delighted my client is satisfied, I don';t like using the gendns alternative as I lose flexibility. If I move to a new server, this site has to make individual DNS changes as we can't do a master change. When you start having exceptions problems can arise, especially since I'm old and forget things.
I really appreciate your efforts on my behalf.

[Matt]

You are exactly correct.

Its better to not make exceptions in hosting unless needed to get things working. Once working, you should go back to your indivdual standards.

So I guess I have a better understanding now. And now you might too?

What we need to figure out is why you are using gendns at all. Your private nameservers should always be working for everyone, at all times. Especially you. Flexibility is why you have them.

If they are not working, open a ticket or just post it here.

A post here is better anyways. As long as you are not giving out passwords, and your password is strong, I don't see a reason for a ticket.