fix: unbound interface naming

This commit is contained in:
Clément Désiles
2025-12-24 17:09:22 +01:00
parent 08364cf2c8
commit 3e469fa25e
3 changed files with 37 additions and 5 deletions
+5
View File
@@ -9,9 +9,14 @@ unbound_custom_vpn_config_path: "{{ unbound_config_base_path }}/vpn.conf"
unbound_custom_lan_domain: "example.lan"
unbound_port: 53
unbound_apparmor_profile_path: /etc/apparmor.d/usr.sbin.unbound
unbound_interface_lan: 192.168.1.1
unbound_interface_vpn: 192.168.27.1
unbound_firewall_allowed_sources:
- { src: "192.168.1.0/24", comment: "DNS from LAN" }
- { src: "192.168.27.0/27", comment: "DNS from VPN" }
unbound_custom_lan_records:
"example.lan":
v4: 192.168.1.2
+5 -5
View File
@@ -8,13 +8,13 @@ server:
# listening port
port: {{ unbound_port }}
# Allow binding to interfaces that don't exist yet (e.g., WireGuard at boot)
# Allow binding to IP addresses that don't exist yet (e.g., WireGuard at boot)
ip-freebind: yes
# Define interfaces binds
interface: lo
interface: lan0
interface: wg0
# 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