Chris Buijs
Chris Buijs
> I believe it's best to leave `ttl-min` and `ttl-max` to form a lower/upper bound on the value. Yeah, that was my thinking as well, maybe not clear in my...
> There's a draft implementation on the `issue-242` branch. The value for `ttl-select` can be "lowest", "highest", "average", "first", "last". They should all be implemented, but I only tested on...
> With regards to `percentile`, I'm not yet clear on what that calculation should look like. If 90%+ of records have the same value use that? No, it is simpler,...
Some notes: - Some of the comments/text in `ttl-modifier.go` still contain "average" on the non-average functions. - When **no** `ttl-select` is provided, RouteDNS exits with message `ttl-select value: "` -...
Another suggestion: `ttl-select = "random"` It would select a random number between `ttl-min` and `ttl-max`.
Works as expected, please Merge.
BTW, As potential alternative... See #242, putting the TTL/Optimize-TTL behind the cache, we can already influence storage in cache more (no need to modify current `cache` code). You lose the...
See NextDNS as an example how to utilize it for "identification" purposes, but I think it would be awesome if we can turn into something where based on the identification...
Couldn't we just add a parameter `paths` (similar to `routers`) to the DOH listener to create "rules"? Example: ``` [listeners.doh] address = "[::]:443" protocol = "doh" resolver = "default" #...
Path should be fine. Hostname would mean we could have similar features with DoT/DoQ for example. That was more my thinking.