diff options
Diffstat (limited to '')
| -rw-r--r-- | kubernetes/pihole/pi-hole.conf | 77 | ||||
| -rw-r--r-- | kubernetes/pihole/resolvconf_resolvers.conf | 20 |
2 files changed, 97 insertions, 0 deletions
diff --git a/kubernetes/pihole/pi-hole.conf b/kubernetes/pihole/pi-hole.conf new file mode 100644 index 0000000..35bbf56 --- /dev/null +++ b/kubernetes/pihole/pi-hole.conf @@ -0,0 +1,77 @@ +server: + # If no logfile is specified, syslog is used + logfile: "/var/log/unbound/unbound.log" + verbosity: 0 + + interface: 127.0.0.1 + port: 5335 + do-ip4: yes + do-udp: yes + do-tcp: yes + + # May be set to yes if you have IPv6 connectivity + 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: "/var/lib/unbound/root.hints" + + # 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 + + # 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 + prefetch: yes + + # 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 + + tls-cert-bundle: "/etc/ssl/certs/ca-certificates.crt" + # tls-cert-bundle: /etc/unbound/unbound_server.pem + hide-identity: yes + hide-version: yes + minimal-responses: yes + qname-minimisation: no + verbosity: 1 + cache-max-ttl: 14400 + cache-min-ttl: 1200 + rrset-roundrobin: no diff --git a/kubernetes/pihole/resolvconf_resolvers.conf b/kubernetes/pihole/resolvconf_resolvers.conf new file mode 100644 index 0000000..c8761e6 --- /dev/null +++ b/kubernetes/pihole/resolvconf_resolvers.conf @@ -0,0 +1,20 @@ +# Generated by resolvconf + +#forward-zone: + #name: "." + #forward-addr: 2a03:ef40:0:3::4 + #forward-addr: 2a03:ef40:0:3::5 +forward-zone: + name: "." + forward-tls-upstream: yes + forward-first: no + forward-addr: 8.8.8.8@853#dns.google + forward-addr: 1.1.1.1@853#one.one.one.one # cloudflare primary + forward-addr: 9.9.9.9@853 # quad9.net primary + forward-addr: 149.112.112.112@853#dns.quad9.net + forward-addr: 1.0.0.1@853#one.one.one.one # cloudflare secondary + forward-addr: 8.8.4.4@853#dns.google + forward-addr: 2606:4700:4700::1111@853#cloudflare-dns.com + forward-addr: 2606:4700:4700::1001@853#cloudflare-dns.com + forward-addr: 2a03:ef40:0:3::4 + forward-addr: 2a03:ef40:0:3::5 |