I migrated my config from the deprecated old DHCP and currently have Dnsmasq as my primary DNS on port 53 and Unbound as the upstream provider on port 53053. To my understanding, the new default config is Unbound as the primary and Dnsmasq just used for DHCP. I think I would rather this setup but when I try making Unbound the primary, my network breaks and DHCP stops working. I just want to restart my DNS and DHCP settings to the new default but have had difficulty finding references for the actual default settings. Does anyone have them that they can post or know of a way that I can just reset my Unbound and Dnsmasq settings to factory default and not my whole config? Thank you.
As a sidenote, I feel like having the default settings somewhere like as a third column on this page would be really helpful for when you bork something up https://docs.opnsense.org/manual/unbound.html
https://docs.opnsense.org/manual/dnsmasq.html#configuration-examples
Quote from: Boxer on Today at 08:08:11 AMhttps://docs.opnsense.org/manual/dnsmasq.html#configuration-examples
Are `lan.internal` and 'guest.internal' standard variable names for lan traffic or is that something I have to setup separately or if I've never done anything with those names can I just ignore that part? I just want DNS resolution in Unbound and DHCP in Dnsmasq, that isn't necessary for that right?
Quote from: opnsense1 on Today at 07:18:31 AMa way that I can just reset my Unbound and Dnsmasq settings to factory default and not my whole config?
I haven't tried this, but there is System -> Configuration -> Defaults -> Components (then select "Unbound..." and "Dnsmasq..."). Backup before attempting this would be recommended ;)
Quote from: opnsense1 on Today at 09:46:17 AMAre `lan.internal` and 'guest.internal' standard variable names for lan traffic or is that something I have to setup separately or if I've never done anything with those names can I just ignore that part? I just want DNS resolution in Unbound and DHCP in Dnsmasq, that isn't necessary for that right?
Not variables - it would be any internal DNS domains that you're using. If you've not setup anything special there, it would be whatever is configured for "Domain" at System -> Settings -> General
Quote from: opnsense1 on Today at 09:46:17 AMQuote from: Boxer on Today at 08:08:11 AMhttps://docs.opnsense.org/manual/dnsmasq.html#configuration-examples
Are `lan.internal` and 'guest.internal' standard variable names for lan traffic or is that something I have to setup separately or if I've never done anything with those names can I just ignore that part? I just want DNS resolution in Unbound and DHCP in Dnsmasq, that isn't necessary for that right?
You need to set up the query forwarding yes. So 'lan.internal' or just 'internal' works. Ignore the guest network if that's not something you need
Thank you for the help! I followed the guide, ignoring guest.internal and just following the steps for lan.internal. Especially the tip about `If all PTR records for 192.168.0.0/16 should be handled by Dnsmasq, creating a single entry with 168.192.in-addr.arpa is enough.` helped. It seems to have worked, super painlessly! I thought I'd have to reconfigure my DHCP and IP reservations but it all reconnected as it was before and I can see device names in my Unbound stats as I was hoping!
The only snag being that I had a host setup in Dnsmasq to make the url tipi.lan work on my network, pointing to a local server, and that seems to no longer work after the transition. I tried setting an Override for it in Unbound but it also still doesn't work. I also tried setting a rule for it in Query Forwarding the same way I did for `168.192.in-addr.arpa` hoping it would forward the request to Dnsmasq and work like before but that also didn't work. What's the proper way to go about this?
Actually I'm not sure why it didn't work when I first tested it - setting an Override in Unbound is working correctly now. 🥳
Thank you for the help everyone!
Forwarding "lan.internal" won't do anything unless you're using "lan.internal" as your internal domain. The point of this is so clients (pointing to Unbound) can resolve things like "my_homelab_server.internal", where that hostname is assigned by dnsmasq DHCP. If you don't care about being able to resolve domains like that, you don't need to do the fowarding at all...