[GH-ISSUE #4] Make the TTL of the dyn-domains configurable #2

Closed
opened 2026-03-04 14:56:09 +03:00 by kerem · 1 comment
Owner

Originally created by @jareware on GitHub (Aug 8, 2018).
Original GitHub issue: https://github.com/futurice/alley-oop/issues/4

The TTL set for the A records (for example) is defined here:

github.com/futurice/alley-oop@a80e24d0fd/dns.go (L34)

as 300. For our use case, a much larger value would make sense.

Making this configurable would probably be the nicest option.

Originally created by @jareware on GitHub (Aug 8, 2018). Original GitHub issue: https://github.com/futurice/alley-oop/issues/4 The TTL set for the A records (for example) is defined here: https://github.com/futurice/alley-oop/blob/a80e24d0fd0218ad00c3b13713e5f0c1a3c0df59/dns.go#L34 as 300. For our use case, a much larger value would make sense. Making this configurable would probably be the nicest option.
kerem closed this issue 2026-03-04 14:56:09 +03:00
Author
Owner

@sevesalm commented on GitHub (Sep 5, 2018):

Closed in #5

<!-- gh-comment-id:418707281 --> @sevesalm commented on GitHub (Sep 5, 2018): Closed in #5
Sign in to join this conversation.
No labels
pull-request
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/alley-oop#2
No description provided.