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.
If not, the cached value should expire within a day of your change.
Hope this helps. --PSRC
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?
--
========================================================
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
========================================================
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