8.8.8.8 has way outdated information

26 views
Skip to first unread message

anywho

unread,
Jan 11, 2010, 3:21:14 PM1/11/10
to public-dns-discuss
I updated dns records for a host (private so I can't share
unfortunately). Every major dns has updated the IP (my serial was
2010011001 and I changed it to 20101101 today and reloaded just to
boost it even more).

opendns, 4.2.2.4 etc are all showing the correct IP. Seems google's
public dns is far too agressivly caching, or something else is broken
with it.

Paul S. R. Chisholm

unread,
Jan 11, 2010, 3:26:10 PM1/11/10
to public-dn...@googlegroups.com
Can you share it privately with someone associated with Google Public
DNS, who can then investigate (or flush the cached value)?

If not, the cached value should expire within a day of your change.

Hope this helps. --PSRC

Gordon

unread,
Jan 11, 2010, 6:30:59 PM1/11/10
to public-dns-discuss
My zone file's SOA record has a min TTL of 3 hours (10800). dig
returns a TTL of 42647 on my domain from Google's Public DNS. Why does
it use a TTL higher than what's specified in my zone file?

Alex Nizhner

unread,
Jan 12, 2010, 9:03:30 AM1/12/10
to public-dn...@googlegroups.com
My zone file's SOA record has a min TTL of 3 hours (10800). dig
returns a TTL of 42647 on my domain from Google's Public DNS. Why does
it use a TTL higher than what's specified in my zone file?


The SOA minimum TTL in your zone file specifies the *lowest* TTL any record in your zone can have.  Resolvers will see TTLs *at least* as long as the SOA minimum.

Alex
 
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================


Gordon

unread,
Jan 12, 2010, 9:39:52 AM1/12/10
to public-dns-discuss
On Jan 12, 9:03 am, Alex Nizhner <nizh...@google.com> wrote:
> > My zone file's SOA record has a min TTL of 3 hours (10800). dig
> > returns a TTL of 42647 on my domain from Google's Public DNS. Why does
> > it use a TTL higher than what's specified in my zone file?
>
> The SOA minimum TTL in your zone file specifies the *lowest* TTL any record
> in your zone can have.  Resolvers will see TTLs *at least* as long as the
> SOA minimum.

I see. The delay is frustrating but I can understand the need to
balance up-to-date information and bandwidth/load.

Although, I would expect that a name that is resolved relatively
infrequently could stand to have a lower TTL since it wouldn't incur
much more load.

Ciao,
Gordon

Reply all
Reply to author
Forward
0 new messages