DnsMasq not working after updating to OPNSense 25.

[franco]

# pluginctl -f dnsmasq


Cheers,
Franco

[trigg3r]

I exported and re-imported the modified config.xml file.

After rebooting the OPNSense WebUI shows Unbound running and DnsMsq stopped, but ...

- checking from the terminal: both are stopped!

- I ping a hostname from a PC and it respond, so name resolution seems to work somehow ...

- but any changes made from the WebUI have no effect: I can change the override settings for the hosts or start/stop Unbound/DnsMaq ... nothing happens

It seems that the WebUI fro this two services is totally disconnected from the operating system settings.

What do you suggest I try?

[Patrick M. Hausen]

How do you check from the terminal?

[trigg3r]

How do you check from the terminal?

root@gw:~ # service dnsmasq status
dnsmasq is not running.

root@gw:~ # service unbound status
unbound is not running.

[Patrick M. Hausen]

OPNsense does not use rcng aka "service" - that's why I asked.

[franco]

What version are you even using? "service dnsmasq status" should also work on 25.1.6 but it's not a given for older service integrations.

# configctl unbound status
# configctl dnsmasq status

These should work regardless because they use the same channel as the service widget ;)


Cheers,
Franco

[trigg3r]

It's fine for me to switch to Unbound. What commands should I run to check unbound service status and start it?

What seems strange to me is that, for example, if I change the IP address of a hostname in the unbound configuration, I expect that a ping to this hostname will return the new IP, but this does not happen...

[meyergru]

Are you talking abozt changing an override or an ISC DHCP reservation or DHCP lease? Does a DHCP reservation/lease exist and you have to respective options in Unbound activated?

1. DHCP leases only time out after the lease expires. Until then, they are still visbile in Unbound if active.
2. DHCP static reservations will only be changed / detected when Unbound is restarted.
3. Generally, your client machines cache DNS answers. On Windows, you can clear that cache via "ipconfig /flushdns".