Google DNS Server is Fast But Killing Sites

[BZB]

After checking Google DNS for few days I did find it faster, BUT (And
a Big BUT)

There's sites that not loading, Google does not resolved the right
IP's.
I found it out because I just changed Server few days ago and I had
some DNS configuration issues.

For few minutes my DNS was publishing my internal IP's.
I fixed it right away, but Google still shows my Internal IP's.

I tried OpenDns , TimeWarner, ATT DNS Servers, and all of them working
fine (Yes, Even ATT)

If I use Google as DNS none of my sites is loading.
when I run nslookup mysite.com I get:

Non-authoritative answer:
Name: mysite.com
Address: 10.10.10.43

10.10.10.43 is my Internal IP for this domain.

Google New DNS Is putting my sites down.....

[Paul S. R. Chisholm]

Sorry to hear that; let's see what's going on.

Is "mysite.com" the name you're trying to resolve? If so, I'm seeing
the same result for all the open resolvers I tried. Here's AT&T and
Google Public DNS:

$ nslookup mysite.com 68.94.156.1
Server: 68.94.156.1
Address: 68.94.156.1#53

Non-authoritative answer:
Name: mysite.com
Address: 64.136.20.67

$ nslookup mysite.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: mysite.com
Address: 64.136.20.67

If there's some other name you're trying to resolve, I have a
hypothesis of what could have happened. You changed the DNS
configuration of your site, and accidentally published an internal IP
address. You might also have published a very long "time-to-live" for
that address. Google Public DNS, like any DNS server, will "cache"
(store) that result for that amount of time.

If that's the case, the problem may have already cleared up.

If you're still having problems, please post (or e-mail) the name
you're trying to resolve. Google Public DNS staff can manually flush
the cached result. Once that's done, Google Public DNS will pick up
the updated DNS configuration information you've published, and you
should get the correct results.

Hope this helps. --PSRC (Google Public DNS software engineer)

P.S.: As some of you already know, some public DNS services have a web
interface to let users (or anyone) flush the cached result for any
name. Most such services don't.