Hi friends,
I need some help with testing dnsmasq. There were issues on Debian systems where systemd-resolved is running because it conflicts with the current dnsmasq implementation.
You can find more information in the issue.
You can check the interface bindings with the ss command:
ss -tulpn | grep ":53"
On Debian with enabled systemd-resolved you should get a result like this:
udp UNCONN 0 0 127.0.0.54:53 0.0.0.0:* users:(("systemd-resolve",pid=516,fd=20))
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=516,fd=18))
tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=516,fd=19))
tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* users:(("systemd-resolve",pid=516,fd=21))
The new approach is to let dnsmasq just listen to the configured interface instead of all interfaces to not conflict with systemd-resolved anymore.
So if you’re using Debian for your NethServer and no Samba which would conflict with dnsmasq, please help by testing dnsmasq.
To install the testing version:
add-module ghcr.io/nethserver/dnsmasq:1.3.1-dev.1
…or to upgrade to the testing version from Software Center or from CLI: (adapt dnsmasq1 to your dnsmasq instance)
api-cli run update-module --data '{"module_url":"ghcr.io/nethserver/dnsmasq:1.3.1-dev.1","instances":["dnsmasq1"]}'
Check if dnsmasq is still working by trying to resolve a DNS record and if it just binds to the configured interface and to 127.0.0.1, see also the test case from the issue.
Thanks in advance for your help.