Only the first dnsmasq instance is parsed correctly. Further definitions are interpreted as dhcp instances. Adding a ‘set -x’ to /etc/init.d/dnsmaq shows that the following setup config dnsmasq ‘main’ option domainneeded '1' ... config dnsmasq ‘tor’ option domainneeded '1' ... is parsed as: config dnsmasq ‘main’
Running multiple dnsmasq instances bound only to specific interfaces solves this issue. This was already requested in the old OpenWRT bug tracker (see here), and patches were developed. Maybe this can finally be included into the mainline source, so people can take advantage of this.
28.12.2021 · Running multiple dnsmasq instances as DNS forwarder and/or DHCPv4 server, each having their own configuration and lease list can be configured by creating multiple dnsmasq sections. Typically in such configs each dnsmasq section will be bound to a specific interface by using the interface list; assigning sections like dhcp , host , etc. to a specific …
#8862 (Multiple instances of dnsmasq (multiple DNS servers/forwarders)) – OpenWrt Modify ↓ Opened 7 years ago Last modified 18 months ago #8862 new enhancement Multiple instances of dnsmasq (multiple DNS servers/forwarders) Description ¶ The patch changes /etc/init.d/dnsmasq: daemon uses pid files instead of killall