116 lines
4.9 KiB
Django/Jinja
116 lines
4.9 KiB
Django/Jinja
# {{ ansible_managed }}
|
|
# see: https://unix.stackexchange.com/a/617194
|
|
# see: https://unix.stackexchange.com/questions/617091/can-you-specify-a-different-configuration-for-different-interfaces-in-unbound
|
|
# see: https://www.dnsleaktest.com
|
|
server:
|
|
verbosity: 0
|
|
|
|
# listening port
|
|
port: {{ unbound_port }}
|
|
|
|
# Allow binding to IP addresses that don't exist yet (e.g., WireGuard at boot)
|
|
ip-freebind: yes
|
|
|
|
# Define interface binds by IP address
|
|
interface: 127.0.0.1 # lo
|
|
interface: {{ unbound_interface_lan }} # lan0
|
|
interface: {{ unbound_interface_vpn }} # wg0
|
|
|
|
# Define access controls (note that ufw might be also configured)
|
|
access-control: 0.0.0.0/0 refuse
|
|
access-control: 127.0.0.0/8 allow # lo interface
|
|
access-control: 192.168.1.0/24 allow # lan0 interface
|
|
access-control: 192.168.27.0/27 allow # wg0 interface
|
|
access-control: ::0/0 refuse
|
|
access-control: ::1 allow
|
|
|
|
# Specify custom local answers for each interface by using views:
|
|
access-control-view: 192.168.1.56/24 lan
|
|
access-control-view: 192.168.27.1/27 vpn
|
|
|
|
do-ip4: yes
|
|
do-udp: yes
|
|
do-tcp: yes
|
|
do-ip6: yes
|
|
|
|
# You want to leave this to no unless you have *native* IPv6. With 6to4 and
|
|
# Terredo tunnels your web browser should favor IPv4 for the same reasons
|
|
prefer-ip6: no
|
|
|
|
# Use this only when you downloaded the list of primary root servers!
|
|
# If you use the default dns-root-data package, unbound will find it automatically
|
|
root-hints: "{{ unbound_root_hints_path }}"
|
|
|
|
# enable to not answer id.server and hostname.bind queries.
|
|
hide-identity: yes
|
|
|
|
# enable to not answer version.server and version.bind queries.
|
|
hide-version: yes
|
|
|
|
# Trust glue only if it is within the server's authority
|
|
harden-glue: yes
|
|
|
|
# Require DNSSEC data for trust-anchored zones, if such data is absent, the zone becomes BOGUS
|
|
harden-dnssec-stripped: yes
|
|
|
|
# Don't use Capitalization randomization as it known to cause DNSSEC issues sometimes
|
|
# see https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378 for further details
|
|
use-caps-for-id: no
|
|
|
|
# the time to live (TTL) value lower bound, in seconds. Default 0.
|
|
# If more than an hour could easily give trouble due to stale data.
|
|
cache-min-ttl: 3600
|
|
|
|
# the time to live (TTL) value cap for RRsets and messages in the
|
|
# cache. Items are not cached for longer. In seconds.
|
|
cache-max-ttl: 86400
|
|
|
|
# Reduce EDNS reassembly buffer size.
|
|
# IP fragmentation is unreliable on the Internet today, and can cause
|
|
# transmission failures when large DNS messages are sent via UDP. Even
|
|
# when fragmentation does work, it may not be secure; it is theoretically
|
|
# possible to spoof parts of a fragmented DNS message, without easy
|
|
# detection at the receiving end. Recently, there was an excellent study
|
|
# >>> Defragmenting DNS - Determining the optimal maximum UDP response size for DNS <<<
|
|
# by Axel Koolhaas, and Tjeerd Slokker (https://indico.dns-oarc.net/event/36/contributions/776/)
|
|
# in collaboration with NLnet Labs explored DNS using real world data from the
|
|
# the RIPE Atlas probes and the researchers suggested different values for
|
|
# IPv4 and IPv6 and in different scenarios. They advise that servers should
|
|
# be configured to limit DNS messages sent over UDP to a size that will not
|
|
# trigger fragmentation on typical network links. DNS servers can switch
|
|
# from UDP to TCP when a DNS response is too big to fit in this limited
|
|
# buffer size. This value has also been suggested in DNS Flag Day 2020.
|
|
edns-buffer-size: 1232
|
|
|
|
# Perform prefetching of close to expired message cache entries
|
|
# This only applies to domains that have been frequently queried
|
|
# NOTE: Disabled because prefetch doesn't work with subnet module (views)
|
|
# see: https://unbound.docs.nlnetlabs.nl/en/latest/manpages/unbound.conf.html#unbound-conf-prefetch
|
|
prefetch: no
|
|
|
|
# One thread should be sufficient, can be increased on beefy machines.
|
|
# In reality for most users running on small networks or on a single machine,
|
|
# it should be unnecessary to seek performance enhancement by increasing num-threads above 1.
|
|
num-threads: 1
|
|
|
|
# Ensure kernel buffer is large enough to not lose messages in traffic spikes
|
|
so-rcvbuf: 1m
|
|
|
|
# Ensure privacy of local IP ranges
|
|
private-address: 192.168.0.0/16
|
|
private-address: 169.254.0.0/16
|
|
private-address: 172.16.0.0/12
|
|
private-address: 10.0.0.0/8
|
|
private-address: fd00::/8
|
|
private-address: fe80::/10
|
|
|
|
# Allow the domain (and its subdomains) to contain private addresses.
|
|
# local-data statements are allowed to contain private addresses too.
|
|
private-domain: "{{ unbound_custom_lan_domain }}"
|
|
|
|
# Enable DNSSEC
|
|
auto-trust-anchor-file: "{{ unbound_anchor_root_key }}"
|
|
|
|
include: "{{ unbound_custom_lan_config_path }}"
|
|
include: "{{ unbound_custom_vpn_config_path }}"
|