f795128f21
Given the volume and ephemeral nature of the nodes we are running jobs on, we're interested in raising the minimum TTL to ensure we're not needlessly querying domains all the time. Some domains such as github.com or fedoraproject.org have low TTLs and we suspect there is a correlation between their low TTLs and the fact that we're seeing increased DNS lookup rates for these domains. Change-Id: I6d9656cb07a694fc2f54f256a63af814c034ffb8
25 lines
1.1 KiB
YAML
25 lines
1.1 KiB
YAML
# OpenDNS
|
|
unbound_primary_nameserver_v6: "2620:0:ccc::2"
|
|
unbound_primary_nameserver_v4: "208.67.222.222"
|
|
|
|
# Google
|
|
unbound_secondary_nameserver_v6: "2001:4860:4860::8888"
|
|
unbound_secondary_nameserver_v4: "8.8.8.8"
|
|
|
|
# Time to live maximum for RRsets and messages in the cache.
|
|
# Default is 86400 seconds (1 day). If the maximum kicks in,
|
|
# responses to clients still get decrementing TTLs based on the
|
|
# original (larger) values. When the internal TTL expires, the
|
|
# cache item has expired. Can be set lower to force the resolver
|
|
# to query for data often, and not trust (very large) TTL values.
|
|
unbound_cache_max_ttl: 86400
|
|
|
|
# Time to live minimum for RRsets and messages in the cache.
|
|
# Default is 0. If the minimum kicks in, the data is cached for
|
|
# longer than the domain owner intended, and thus less queries are
|
|
# made to look up the data. Zero makes sure the data in the cache
|
|
# is as the domain owner intended, higher values, especially more
|
|
# than an hour or so, can lead to trouble as the data in the cache
|
|
# does not match up with the actual data any more.
|
|
unbound_cache_min_ttl: 0
|