os-adguardhome-maxit needs to support opnsense system DNS port

[yvovandoorn]

One of the new features in Opnsense 23.1.6 is:

system: register DNS service ports for unified use across core and plugins

However for those using os-adguardhome-maxit with Opnsense 23.1.6, the DHCP server no longer hands out a DNS server as os-adguardhome-maxit isn't advertising that its running the DNS service.

See opnsense/core#6513 for more information, specifically opnsense/core#6513 (comment).

There is a workaround for those using DHCPv4 to manually specify the DNS server in the DHCPD configuration -- but this doesn't work for those using DHCPv6 with dynamic prefix.

[mikeodr]

I am not running adguard home and I saw this exact problem.

I had to apply the workaround to get this to work.

What I am running is the nextdns resolver on port 53, and then having local unbound resolver running on a different port.

I suspect based on reading the forums it is this change:
opnsense/core@9f6df9e

The "workaround" may be necessary if this change remains permanent.

[SentenOnGithub]

Update v1.9 solved the issue.
Do not forget to set the new checkbox in Services > AdGuardHome > General, as I did ::)

Plugin Changelog

1.9

• Fix DNS settings introduced with 23.1.6
• Update to latest version

[mimugmail]

Thx for the feedback