starred/nsupdate.info-nsupdate-info

Fork 0

mirror of https://github.com/nsupdate-info/nsupdate.info.git synced 2026-04-25 08:35:56 +03:00

[GH-ISSUE #51] DNS TTL configurable #51

New issue

Open

opened 2026-02-26 09:35:12 +03:00 by kerem · 7 comments

kerem commented

2026-02-26 09:35:12 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Oct 22, 2013).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/51

Samuirai wrote:
default is 60. create a user changeable field in a range.

Originally created by @ThomasWaldmann on GitHub (Oct 22, 2013). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/51 Samuirai wrote: default is 60. create a user changeable field in a range.

kerem added the

enhancement

label

2026-02-26 09:35:12 +03:00

kerem commented

2026-02-26 09:35:13 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 22, 2013):

ThomasWaldmann wrote:
add an attribute to Host model.

@ThomasWaldmann commented on GitHub (Oct 22, 2013): ThomasWaldmann wrote: add an attribute to Host model.

kerem commented

2026-02-26 09:35:13 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Nov 4, 2013):

hmm, i was thinking about it - the usefulness of such a setting is limited to specific scenarios.

for dynamic hosts that get accessed rather often and that change ip rather often, one wants the minimum allowed TTL.

only for hosts that change IP mostly at a predictable non-usage times (like at 4 o'clock in the morning, some routers have such an option), one can live with a longer TTL.

@ThomasWaldmann commented on GitHub (Nov 4, 2013): hmm, i was thinking about it - the usefulness of such a setting is limited to specific scenarios. for dynamic hosts that get accessed rather often and that change ip rather often, one wants the minimum allowed TTL. only for hosts that change IP mostly at a predictable non-usage times (like at 4 o'clock in the morning, some routers have such an option), one can live with a longer TTL.

kerem commented

2026-02-26 09:35:13 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Jan 16, 2014):

will close this as wontfix 3/2014 except if someone finds a good reason to have it configurable for users and speaks up here.

@ThomasWaldmann commented on GitHub (Jan 16, 2014): will close this as wontfix 3/2014 except if someone finds a good reason to have it configurable for users and speaks up here.

kerem commented

2026-02-26 09:35:14 +03:00

Author

Owner

@elnappo commented on GitHub (Jan 17, 2014):

just for info, on dyndns.org you can chose between (and maybe more)

20sec "With TTLs that can be set as low as 20 seconds, extremely fast propagation will happen as soon as your update client notifies us."
60sec "Standard dynamic DNS value"
4h "Static record with benefits of DNS caching"

@elnappo commented on GitHub (Jan 17, 2014): just for info, on dyndns.org you can chose between (and maybe more) - 20sec "With TTLs that can be set as low as 20 seconds, extremely fast propagation will happen as soon as your update client notifies us." - 60sec "Standard dynamic DNS value" - 4h "Static record with benefits of DNS caching"

kerem commented

2026-02-26 09:35:14 +03:00

Author

Owner

@pejakm commented on GitHub (Apr 15, 2015):

DnsExit service supports any value from 2 minutes to 48 hours.

@pejakm commented on GitHub (Apr 15, 2015): DnsExit service supports any value from 2 minutes to 48 hours.

kerem commented

2026-02-26 09:35:14 +03:00

Author

Owner

@UnderEu commented on GitHub (Nov 2, 2023):

https://blog.apnic.net/2019/11/12/stop-using-ridiculously-low-dns-ttls

My personal hosts update IP addresses every 1 or 2 weeks, more or less; I have no need to fetch a new DNS query every 1 minute if my addresses won't change anytime sooner than that. I want the option to set the TTL I want on my hosts, even behind an Advanced panel or some kind of "I know what I'm doing" consent check.

I'm no programmer, I can't contribute with code but I'm available to test things when necessary.

Oh... and this issue doesn't need to wait another 10+ years to be fixed.

@UnderEu commented on GitHub (Nov 2, 2023): https://blog.apnic.net/2019/11/12/stop-using-ridiculously-low-dns-ttls My personal hosts update IP addresses every 1 or 2 weeks, more or less; I have no need to fetch a new DNS query every 1 minute if my addresses won't change anytime sooner than that. I want the option to set the TTL I want on my hosts, even behind an Advanced panel or some kind of "I know what I'm doing" consent check. I'm no programmer, I can't contribute with code but I'm available to test things when necessary. Oh... and this issue doesn't need to wait another 10+ years to be fixed.

kerem commented

2026-02-26 09:35:14 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Nov 2, 2023):

I agree that for rarely changing "static" DNS entries one should of course not use very short TTLs.

But dyndns is usually used for dynamic IPs, the connections are less stable (and often even intentionally disconnected once a day) and often the IP changes when a new (e.g. DSL) connection is established. If one uses a long TTL, that means that after reconnecting, the IP in DNS will be invalid for that long time until all caching DNS servers have refreshed.

Another aspect is the amount of users / amount of DNS queries for such entries. dyndns entries are often used for a very limited group of people (like remote access to home or friends' or customer machines for administrative purposes), so there is no big load on the DNS system caused by this.

So, I personally won't work on this, but if someone wants to make a PR implementing this in the nsupdate.info software, I will review it.

@ThomasWaldmann commented on GitHub (Nov 2, 2023): I agree that for rarely changing "static" DNS entries one should of course not use very short TTLs. But dyndns is usually used for dynamic IPs, the connections are less stable (and often even intentionally disconnected once a day) and often the IP changes when a new (e.g. DSL) connection is established. If one uses a long TTL, that means that after reconnecting, the IP in DNS will be **invalid** for that long time until all caching DNS servers have refreshed. Another aspect is the amount of users / amount of DNS queries for such entries. dyndns entries are often used for a very limited group of people (like remote access to home or friends' or customer machines for administrative purposes), so there is no big load on the DNS system caused by this. So, I personally won't work on this, but if someone wants to make a PR implementing this in the nsupdate.info software, I will review it.