From b8ee2b3a2ffbcea39df7d72b65faffdeec5f2784 Mon Sep 17 00:00:00 2001 From: Courtney Hall Date: Mon, 8 Dec 2025 12:58:10 -0800 Subject: [PATCH] dns/dnsmasq-to-unbound: fix README - remote control enabled by default Unbound remote control is always enabled by default in OPNsense, there is no UI setting to enable it. Updated README to reflect this. --- dns/dnsmasq-to-unbound/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/dns/dnsmasq-to-unbound/README.md b/dns/dnsmasq-to-unbound/README.md index cd7b838ae..85480fc97 100644 --- a/dns/dnsmasq-to-unbound/README.md +++ b/dns/dnsmasq-to-unbound/README.md @@ -14,8 +14,7 @@ This OPNsense plugin automatically registers dnsmasq DHCP leases and static host ## Requirements -- OPNsense with Unbound DNS resolver enabled -- **Unbound Remote Control must be enabled**: Services > Unbound DNS > General > Enable Remote Control +- OPNsense with Unbound DNS resolver enabled (remote control is enabled by default) - dnsmasq plugin installed and configured with DHCP ## Installation @@ -80,7 +79,8 @@ grep dnsmasq_watcher /var/log/system/latest.log ### Common Issues **"Unbound remote control not enabled"** -- Enable Remote Control in Services > Unbound DNS > General +- This should not normally occur as OPNsense enables remote control by default +- Check that Unbound is running and restart if necessary **"No domain configured in dnsmasq.conf"** - Add `domain=lan` (or your domain) to dnsmasq configuration