ISC to Dnsmasq breaks some name resolution

[allenlook]

I've got some weird name resolution going on after the switch to Dnsmasq.

Pretty simple network, one LAN (192.168.1.x), and one DHCP range (192.168.150.. -> ..254), with IPv4 only.

I imported all the static leases from ISC into Dnsmasq and followed the instructions (several times) to set up the DHCP range, Query Forwarding, setting ports 53 (Unbound) and 53053 (Dnsmasq) properly, etc.  All PCs and devices are receiving their DHCP-reserved static assignments, or are getting dynamic addresses so that seems good.

My main server and VMs can no longer access each other by name, and I have had to hard-code the IP addresses for most of them to be able to talk to one another.

Most PCs can ping other PCs on the network by short-name, but not by FQDN (short-name.home.arpa).

The router cannot ping LAN devices at all, whether by short-name or by FQDN.

Any suggestions on where to look?  I appreciate any help!

[allenlook]

It seems I can ping from PC to PC (again only by short-name alone), but not from PC to devices like cameras, garage door openers, etc.

[nero355]

What does nslookup/dig output when you use the FQDN for the DNS query ?
And from which Clients ?

I am guessing you need to tell Unbound about your DNSmasqd existing for certain local domains, but I am not sure, because I am more the "Use Unbound as Upstream DNS Server for DNSmasqd" type of user :)

[Stormscape]

Sounds like you made the same mistake I did, and forgot to tell Unbound about dnsmasq being the authoritative DNS server for your local domain. Make sure to follow the OPNsense hosted guide for setting up dnsmasq