Update not working after config Dnsmasq as primary DNS resolver

Started by UiD, May 14, 2026, 04:22:03 PM

Previous topic - Next topic
Hello,

After configuring Dnsmasq as the primary DNS resolver and Unbound as recurser, updating firmware not working.
Fetching changelog information, please wait... fetch: https://pkg.opnsense.org/FreeBSD:14:amd64/26.1/sets/changelog.txz: Host does not resolve
Dnsmasq was configure with internal dns-server => everything works fine at this level :)

OPNsense in ssh : I ping just the internal DNS Server

If I declare an external DNS server (General Settings) as 1.1.1.1
I can see it appear in the resolv.conf file but ping not working

disable => Allow DNS server list to be overridden by DHCP/PPP on WAN
enable => Do not use the DNS Forwarder/Resolver as a DNS server for the firewall

I have tested several things without success.

any help will be highly appreciated

---------------------------
OPNsense 26.1.7_3-amd64





This seems to be linked to a problem with the LAN DNS rule on the firewall. You just have to find the right one :P

:( I thought the problem was solved but after rebooting it's the case again.

Very strange, if I select 1.1.1.1 I access the System: Firmware: Status menu without problem but I am blocked from downloading.
And if I select my DNS it takes time, I have an hourglass
There must be a subtlety somewhere?



Quote from: UiD on May 14, 2026, 04:22:03 PMdisable => Allow DNS server list to be overridden by DHCP/PPP on WAN
Why not use that simply and allow the updates to go via your ISP's DNS Servers ?!
Weird guy who likes everything Linux and *BSD on PC/Laptop/Tablet/Mobile and funny little ARM based boards :)

Quote from: nero355 on May 15, 2026, 03:50:32 PM
Quote from: UiD on May 14, 2026, 04:22:03 PMdisable => Allow DNS server list to be overridden by DHCP/PPP on WAN
Why not use that simply and allow the updates to go via your ISP's DNS Servers ?!
It's an Homelab ;)

Today I restore an old configuration from "CRASH" (from scratch :P)
I reinstall all and it's OK now.
I tried to reproduce the problem without success.