Quote from: Monviech (Cedrik) on October 19, 2026, 09:49:43 AMBut why, it's already available in core?Hi Cedrik,
https://docs.opnsense.org/manual/dnsmasq.html#firewall-alias-ipset
my bad, you're actually right! Somehow I overlooked this as I don't use dnsmasq and really haven't checked the recent docs for it.
I checked again why someone would rather use the new plugin than dnsmasq's option and to conclude first: Keep using dnsmasq and use it for this case. It will work perfectly fine! 100% agree.
Some things to mention though:
- For people (like me) using Adguard Home + Unbound DNS, this is a good option and easy to use
- My plugin uses the DNS TTLs instead of fixed windows and prunes
- dnsmasq's ipset code only adds A/AAAA addresses. The plugin also adds ipv4hint/ipv6hint from HTTPS and SVCB records
- The plugin can return a SERVFAIL if it can't update the ipset, dnsmasq would not do that, potentially resulting in a not-working allow rule
- And the plugin has some more GUI based Stats/Learned Addresses.
So I don't say the dnsmasq option is not good. It definitely is! And everyone where this works and is sufficient should use it, as it's also not only covered by community effort.
For everyone else, especially the occasional admin or people who use different DNS setups, the Plugin might be very handy (as it is for me).
So I would say, both are good options and have their use cases.
Have a nice day and thanks for replying :)
"