Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'd kind of like if there was some ability to have more complex multi-part TTLs as an option along with a default TTL (the current one). So I could specify

  Default TTL: 12 hours;
  [<startdate> to <enddate>] TTL: 10 minutes;
or even

  Default TTL: 12 hours;
  [Thu 0000-1200, repeating]: 5 minutes;
  [<startdate> to <enddate>] TTL: 10 minutes;
So with no further effort all downstream caches/clients can basically have advanced notice of regular maintenance windows as well as planned maintenance and just automatically adapt. Of course this wouldn't deal with true emergencies, but it might lower the overhead for a huge amount of regular stuff that otherwise tempts people to set it low and leave it that way.

I dunno, I'm sure there's other downsides I haven't thought of, and proper implementation would require thinking through side effects. But after a long time dealing with it feels like there's some room for something beyond one single TTL ever which must be specifically changed (with a wait for propagation) well ahead of time whenever anything planned with a risk of issues needs to be done. Maybe?



I don't think you'd need to further complicate DNS, just have a service running that checks a calendar and syncs your DNS TTLs appropriately.

eg.

- Check if there's a maintenance window in the next [max TTL]

- If not, set TTL = [max TTL]

- Otherwise, set TTL = [time until maintenance window]

- Repeat




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: