Limit TTL

[bwbroersma]

@janwillemstegink had an idea to limit the TTL, I said this was already done:

Internet.nl/docker/resolver/resolver-permissive.conf.template

Lines 15 to 16 in d3abfb5

	cache-max-ttl: 60
	cache-max-negative-ttl: 60

But these are not yet deployed in v1.8.5, I tested a domain with a TTL record of a week, and it's indeed still cached.
Fixed with 47fa821 from merge:

• Limit cache-max-negative-ttl in resolving #1292

Close this issue if it's deployed?

[bwbroersma]

@mxsasha: I see the TTL is both set as context and in a config file? The code settings seems redundant to the unbound conf?

Internet.nl/checks/tasks/__init__.py

Lines 40 to 41 in c025ade

	self._ub_ctx.set_option("cache-max-ttl:", str(settings.CACHE_TTL * 0.9))
	self._ub_ctx.set_option("cache-max-negative-ttl:", str(settings.CACHE_TTL * 0.9))

What should I now see on v1.8.5 single-test? Since it seems higher than the max caching of 200 * 0.9:

Internet.nl/internetnl/settings.py

Line 260 in c025ade

CACHE_TTL = int(os.getenv("INTERNETNL_CACHE_TTL", 200))

BTW shouldn't this move to the unbound conf too?

Internet.nl/checks/tasks/__init__.py

Line 45 in c025ade

self._ub_ctx.set_option("rrset-roundrobin:", "no")