2019-07-23 11:30:53 +02:00
|
|
|
# Increasing caching
|
2019-07-23 14:09:34 +02:00
|
|
|
# This has potential to increase memory usage to 110m under heavy usage, but
|
|
|
|
|
# I find that unlikely as almost everything is using so short TTLs
|
2019-07-23 11:30:53 +02:00
|
|
|
# See also MEMORY CONTROL EXAMPLE in man unbound.conf
|
|
|
|
|
|
|
|
|
|
server:
|
2023-02-21 18:08:54 +01:00
|
|
|
# bytes in message cache, defaults to 4m
|
|
|
|
|
msg-cache-size: 50m
|
|
|
|
|
# bytes in rrset cache, defaults to 4m
|
|
|
|
|
rrset-cache-size: 50m
|
|
|
|
|
# nxdomain cache, default 1m
|
|
|
|
|
neg-cache-size: 10m
|
|
|
|
|
# Cache results for 15 minutes even if they had a shorter TTL. Cloudflare
|
|
|
|
|
# zone export used to have 1 second, and I have also been seeing 1
|
|
|
|
|
# minute in the wild, I think 5 mins shouldn't break anything, but bigger
|
|
|
|
|
# might.
|
|
|
|
|
cache-min-ttl: 900
|
2024-04-07 16:34:36 +02:00
|
|
|
# Update cache for popular items before they expire. ~10 % traffic
|
|
|
|
|
# increase according to `man unbound.conf`
|
|
|
|
|
prefetch: yes
|
|
|
|
|
# Fetch keys when DS is encountered, lower latency for a bit higher CPU use
|
|
|
|
|
prefetch-key: yes
|
2024-04-07 18:44:10 +02:00
|
|
|
# Allow expired results to be served if they are in cache. The cache will
|
|
|
|
|
# get updated the next time.
|
|
|
|
|
serve-expired: yes
|
2024-04-26 12:53:50 +02:00
|
|
|
# DNSSEC errors for valid and expired records
|
|
|
|
|
ede: yes
|
|
|
|
|
ede-serve-expired: yes
|
2024-04-19 08:14:32 +02:00
|
|
|
|
|
|
|
|
# vim: filetype=unbound.conf
|
