[FS#391] dnsmasq stops working properly if the fastest upstream DNS server returns a server failure

LEDE Bugs lede-bugs at lists.infradead.org
Sun Jan 15 20:58:05 PST 2017


The following task has a new comment added:

FS#391 - dnsmasq stops working properly if the fastest upstream DNS server returns a server failure
User who did this - Stijn Tintel (stintel)

----------
Something similar happens to me from time to time. I'm a Gentoo user, and one of the nameservers for the gentoo.org domain seems to be unreliable. When it is down, it's near impossible for me to resolve anything in said domain.

Someone in OpenWrt also had this problem where he was unable to resolve most records of a domain when connected to hist OpenWrt router. The problem did not occur when he was directly connected.

While searching for possible solutions, I came across the --all-servers option:


By default, when dnsmasq has more than one upstream server available, it will send queries to just one server. Setting this flag forces dnsmasq to send all queries to all available servers. The reply from the server which answers first will be returned to the original requester.


Can you test if enabling it helps? Can be enabled in /etc/config/dhcp:


config dnsmasq
        option allservers '1'
        ...

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=391#comment1270



More information about the lede-bugs mailing list