Messages

If you use the above linked software, you don't have to worry about any of the above concerns.

It will also automatically take care of local PTR/A resolution for all your LAN hostnames (through discovery via arp, mdns, ptr probes and DHCP leases file parsing), and you can delegate queries from subnets, MAC addresses or for custom TLDs to your local unbound instance if you want this.

Or do it the other way around and keep running unbound on UDP 53, and use ctrld as the upstream although you will lose the device identification data in this mode.

It does all the automatic DHCP registering with PTR as well? I didn't read that in the documentation, that is neat!

But still it requires manual CLI configuration for host overrides, aliases and other manual config, right?

Manual host override support (reading of the mappings you have in place) is coming in the next version.

If you use the above linked software, you don't have to worry about any of the above concerns.

It will also automatically take care of local PTR/A resolution for all your LAN hostnames (through discovery via arp, mdns, ptr probes and DHCP leases file parsing), and you can delegate queries from subnets, MAC addresses or for custom TLDs to your local unbound instance if you want this.

Or do it the other way around and keep running unbound on UDP 53, and use ctrld as the upstream although you will lose the device identification data in this mode.

There is a simpler way if you use this DNS daemon, it will relay client info from all your LAN devices and send it to NextDNS: https://github.com/Control-D-Inc/ctrld/wiki/NextDNS-Mode

It's fully compatible with OPNsense.

Heya, I'm from Control D. Your assumption is partially correct, but there are ways to avoid it. See this guide I wrote: https://github.com/Control-D-Inc/ctrld/wiki/pfSense-and-OPNsense-Operations-Guide