[GH-ISSUE #489] Add support for specifying maximum bounds for TTLs #206

Closed
opened 2026-03-07 22:47:51 +03:00 by kerem · 0 comments
Owner

Originally created by @briansmith on GitHub (May 24, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/489

Should Trust-DNS also support maximum values for the TTLs? I could see in Conduit we probably want to poll DNS at least once an our or once a minute, regardless of TTL, just to keep our service discovery reasonably responsive. If someone has a 48 hour TTL then one is going to be very sorry one day if/when it's actually honored.

Originally created by @briansmith on GitHub (May 24, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/489 Should Trust-DNS also support maximum values for the TTLs? I could see in Conduit we probably want to poll DNS at least once an our or once a minute, regardless of TTL, just to keep our service discovery reasonably responsive. If someone has a 48 hour TTL then one is going to be very sorry one day if/when it's actually honored.
kerem 2026-03-07 22:47:51 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#206
No description provided.