๐ก OPNsense Unbound DNS: Ad-blocking โ Executive Summary
Technical architectural analysis, practical configuration manifests, and deployment instructions for OPNsense Unbound DNS: Ad-blocking.
References and Guidelines (NOTE)
System Required:
DNS
Port forwarding
Private domain registration
References and Guidelines (NOTE)
List instructing to allow the response even if the DNS query result includes a private IP address (RFC 1918 address: \$10.x.x.x\$, \$192.168.x.x\$, \$172.16.x.x\$, etc.)
- Redefinition is at a higher level, but registering it is more convenient.
Register Override Host
Client
Apply VPN Client
- Add
DNSinformation to the WireGuard Interface (if there is no band included inAllowedIPs, add it)
txt
[Interface]
PrivateKey = <secret>
Address = 10.0.X.X/32
DNS = 192.168.118.53
[Peer]
PublicKey = <secret>
#AllowedIPs = 0.0.0.0/0
AllowedIPs = 10.0.X.X/24, 118.37.2.0/24, 192.168.118.0/24
Endpoint = <ddns>:41821
PersistentKeepalive = 25Trouble shooting
Leave a Reply