Messages

Following the DHCPv4 with DNS registration example in the documentation, I have migrated from ISC IPv4 to DNSmasq on a test system.
I have unbound on port 53 pointing to DNSmasq on 53053 for local name resolution, as instructed.
It does work, however, resolving and pinging hosts by hostname lags for a long time.
The ping time from one host to another is in the .250 ms range, but it sits there for about 10 seconds thinking about it before spitting out the results.
Opening a browser and navigating to cockpit using machine-hostname.localdomain:9090 is equally as laggy.
Anyone else experiencing this sort of behavior?
For now, ISC with Unbound is working perfectly for me on the main router, so I suppose I will keep it that way for a while.
However, if Unbound pointing to DNSmasq for local domain name resolution is the future, I hope to figure it out.

Unbound is not going anywhere as far as i know, so why not migrate to Kea for DHCP ?

I'm using Unbound as DNS server so i can sort of use it as an adblocker, and for DHCP, i migrated to KEA
Works fine here.

Is there a way to trigger a "save and apply" on an interface without changing anything via command line? Since that's all that i need to do get an ipv6, i believe that would be enough to mitigate.

Any ideas ?

Facing a very strange issue where ipv6 works but everytime opnsense starts, I need to manually go to the wan interface and just save without changing anything. Otherwise it'll just not get ipv6 on the WAN interface and consequently, on all others.

https://imgur.com/a/jD73pc9 Config and interface overview