Testing unbound, cache-max-ttl = 0?

Unbound
1

Hi,

We're trying to run some tests on our systems which use unbound. We had an upstream recursive server fail the other day - which caused a lot more problems than we were expecting (as we use unbound on local machines, forwarding to two recursive servers).

At this stage we think it's either a config / timeout issue (i.e. nothing wrong with unbound) - but we want to test further.

Can you set 'cache-max-ttl: 0' in unbound.conf, to turn off caching?

During our tests we don't want unbound using cached replies to queries - we want to force it to go to the upstream recursive servers every time.

Thanks,

-Karl

2

Hi,

Max-ttl is a bit weird, because then it also returns 0 TTLs to the
clients.

Zero the cache size. There is also the infra cache and key cache.
msg-cache-size: 0
rrset-cache-size: 0

Best regards,
   Wouter

3

Thanks, that worked.

In the end as we suspected, we found the problem wasn't with unbound - it was with a number of services we run that only read /etc/resolv.conf at startup - and hence, didn't see the change from the recursive servers to 127.0.0.1 in resolv.conf (i.e. to use the local instance of Unbound).

Now we've restarted the services - everything works fine, even when one of the upstream recursive's goes offline.

-Karl