The DNS resolvers override low TTLs, setting them to a minimum of 600 seconds. That's... spooky. A lot of DNS records use smaller values, one minute, or five minutes.

Could you lower it again? I think the minimum used to be 30 seconds. Personally, anything <= 60 would make me happy.

(I'm not having problems with specific services, and I probably never will. But other people might, and it just skeeves me out.)

_________________
Matt Nordhoff (aka Peng on IRC)

+1, especially if we don't hammer the dns servers and have just a few requests per minute or so.

Also, reloading the zone more frequent than 15 minutes would also be nice, otherwise the TTL doesn't really matter if you need to wait up to 15 minutes for the changes to take effect.

Not a direct solution, but one way around both issues is to operate with the Linode servers in slave mode - in that case they simply track the master records, and update immediately with master notification.

-- David

He's talking about the resolvers, not the authoritative nameservers. As a test, in Dallas, you can do dig @resolver01.dallas.linode.com imogen.hotellite.net, and you will get a TTL of 600 (replace dallas with your datacenter if you're in a different DC). If you do dig @imogen.hotellite.net imogen.hotellite.net, you'll get a TTL of 60 (imogen.hotellite.net is authoritative for hotellite.net, so you're seeing what I really want the TTL to be).

_________________
Disclaimer: I am no longer employed by Linode; opinions are my own alone.

This was not the intention at all. It should be resolved momentarily.

-Chris

Verified fixed. Thank you!

<3 ♥

_________________
Matt Nordhoff (aka Peng on IRC)