/dev/rob0: > Google Public DNS seems to look up records again before the TTL > expires in their cache, so you are indeed likely to see a slight
There is an article that shows that different resolvers report TTL values in different ways. Begin quote: For a record initially served with a TTL equal to N by authoritative servers: * Google DNS serves it with a TTL in the interval [0, N-1] * dnscache is serving it with a TTL in the interval [0, N] * Unbound serves it with a TTL in the interval [0, N] * Bind serves it with a TTL in the interval [1, N] * PowerDNS Recursor always serves it with a TTL of N End quote. http://00f.net/2011/11/17/how-long-does-a-dns-ttl-last/ Wietse
