Dnsmasq multiple forwarder instances ignore option dnsmasq_config and select faster answering server

[amatsumara]

@lleachii

You don’t have to tell the DHCP to give out it’s own address. This config is used to give out other servers.

In my case dhcp_option change nothing. If it absent default would be router or dhcp server IP (same in my case).

@lleachii

This command seems incorrect…and I’m not certain what traffic you wish to see. If you’re looking for dnsmasq sending requests, you would listen to outbound packets on WAN, udp and dest port 53. If you want to see what your clients are querying, you listen to LAN.

All look good for me. I'm checking dnsmasq sending requests to whatever server except 1.1.1.1. No need to narrow filter more in my case (no requests to dnsmasq from outside net). eth0 is my WAN interface.

@lleachii

Lastly, all Global DNS servers should provide the same answers. You should want your dnsmasq to take the answer of the fastest-responding forwarder. This is normal behavior.

This is not always the case: IANA root servers can't provide information about OpenNIC domains, you not always want your traffic analysed by specific DNS servers and use VPN. That's why strict order exist in dnsmasq configuration.
In this topic I showed exact discrepancy with documentation but in more complex configuration my experiments include VPN tunnels and custom routes to specific DNS servers. Wide use of VPR VPN Policy-Based Routing + Web UI -- Discussion