Works great! LGTM! =)

No issues noted with DHCP/DNS

@nucleo can you share a bit more, what did not work in this update?

With dnsmasq-2.92-1.fc43.x86_64

# dig

; <<>> DiG 9.18.43 <<>>
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14655
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;.                              IN      NS

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Thu Jan 22 19:50:43 EET 2026
;; MSG SIZE  rcvd: 28

With dnsmasq-2.91-1.fc43.x86_64

 dig

; <<>> DiG 9.18.43 <<>>
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21355
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;.                              IN      NS

;; ANSWER SECTION:
.                       87203   IN      NS      h.root-servers.net.
.                       87203   IN      NS      a.root-servers.net.
.                       87203   IN      NS      b.root-servers.net.
.                       87203   IN      NS      c.root-servers.net.
.                       87203   IN      NS      j.root-servers.net.
.                       87203   IN      NS      i.root-servers.net.
.                       87203   IN      NS      g.root-servers.net.
.                       87203   IN      NS      l.root-servers.net.
.                       87203   IN      NS      m.root-servers.net.
.                       87203   IN      NS      d.root-servers.net.
.                       87203   IN      NS      e.root-servers.net.
.                       87203   IN      NS      k.root-servers.net.
.                       87203   IN      NS      f.root-servers.net.

;; Query time: 106 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Thu Jan 22 19:50:05 EET 2026
;; MSG SIZE  rcvd: 239

Can you please create new bug for dnsmasq component in bugzilla, https://bugzilla.redhat.com? This is not what I see, but maybe there is some important difference.

Are you sure the used servers are the same for both versions? Can you please try adding log-queries and check forwarded . to <IP> address, whether it is both expected? But a bug would be better place for an investigation. I cannot reproduce any regression.

This config line makes 2.92 broken address=/#/example.com/ With 2.91 only example.com NXDOMAIN

@nucleo

I cannot reproduce that neither. Used command: echo "address=/#/example.com/" | sudo tee /etc/dnsmasq.d/block.conf && sudo systemctl restart dnsmasq && dig @localhost -t A {,www.,,www.}example.com, in both Fedora 43 with original 2.91 and updated rawhide machine, dnsmasq-2.92-4.fc44.x86_64.

Edit: Oh, okay. they return both nxdomain, but old version resolves addresses with this for unspecified domains. But what should that configuration do? --address=/#/8.8.8.8 is documented in manual page to work with IP addresses. It does not refuse this configuration, But it is supposed to be followed by IP addresses. Like:

echo "address=/#/8.8.8.8" | sudo tee /etc/dnsmasq.d/block.conf && sudo systemctl restart dnsmasq && dig @localhost -t AAAA example.{com,org}

That means, I think it works as it should. Yes, there were some changes in that code, but what you use seems undocumented behaviour to me. It has different meaning with --server directive, but then it should be used last, instead of ip addresses. I think I can let this update pass.