Stop using low DNS TTLs

Re:Stop using low DNS TTLs by skybrian on Sunday November 03, 2019 @04:50PM (#21436908)

I'm wondering what it would take to make a DNS caching service with updates based on reliable notifications rather than polling? After all, every cellphone does it.

[ Parent | on HN ]

Re:Stop using low DNS TTLs by diegocg on Sunday November 03, 2019 @05:24PM (#21437143)

This already exists (NOTIFY), but it's only used for master-slave setups (ie. a bunch of DNS servers serving some authoritative zone who want changes to be transmitted to all slaves ASAP)

It would be interesting to (ab)use this mechanism in the way you suggest. A recursive DNS server could ask to be NOTIFY'ed of changes in the zone they are querying...it would, of course, add load to the server, and it would need strict limits to avoid DoS, but it seems an interesting idea.

[ Parent | on HN ]

Re:Stop using low DNS TTLs by dsp on Sunday November 03, 2019 @05:57PM (#21437343)

The big problem, to the extent there is one, is between the client and the recursive server. Not as much the recursive and the authoritative. Cost is highly amortized between recursive and authoritative for busy names.

[ Parent | on HN ]

Re:Stop using low DNS TTLs by shinwn on Sunday November 03, 2019 @08:48PM (#21438296)

DNS Push Notifications[1] could be tacked on to resolvers and clients.

1: https://tools.ietf.org/html/draft-ietf-dnssd-push

[ Parent | on HN ]