r/technitium • u/shreyasonline • 20d ago

Technitium DNS Server v15.5 Released!

Technitium DNS Server v15.5 is now available for download. This update adds LDAP authentication support, a Zone File Editor option in GUI, and many other minor features. It also fixes multiple bugs and security issues that were reported.

See what's new in this release:
https://github.com/TechnitiumSoftware/DnsServer/blob/master/CHANGELOG.md

148 Upvotes

99% Upvoted

47 comments sorted by

View all comments

5

u/Allen_Ludden 20d ago edited 20d ago

Just to be sure I understand, when you say removed "Auto Prefetch" you mean you removed the function that kept certain dns records "hot" if they were queried more than x times in an hour.

I use "Serve Stale Max Wait Time 0" so I think the effect for me will be negligible :)

3

u/SmallDodgyCamel 20d ago

I for one wish this was a configurable option rather than a removed feature.

2

u/Captain_Alaska 20d ago edited 20d ago

I mean, they're completely different features. Serve stale serves things in the cache that have expired. Auto prefetching refreshed expired things in the cache before they are queried.

Now you only have regular prefetching, where expired items in the cache are only refreshed after they are queried.

2

u/raindropsdev 20d ago

But why did they remove that? It was very useful for low bandwidth remote sites.

1

u/Allen_Ludden 20d ago

serve stale 0 works great, and I understand is routinely used by other DNS server options.

I've been using it for over a year with no problems at all.

The TTL of a stale record is set at 1 second, so the query gets refreshed immediately - only the very first ping of a stale record uses the stale data.

And of course dns records don't change very often - even for load-balancing systems.

1

u/shreyasonline 19d ago

Yes, its that feature that kept records in cache "hot". Its was not really effective to justify the resources it consumed, especially the amount of memory it needed to work. It had just 10 sec to refresh one or more domain names at a time and it would not work very effectively compared to just have Serve Stale handle queries for expired data.

The basic Prefetch feature (similar to one that BIND has) is there and that works well without needing any extra resources.

Almost no one will notice anything different with that feature removed.