@filippo_carletti I found the culprit!!!
In redhat the next bug report describes the issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1400909
dnsmasq in nethaserver uses:
cat /etc/e-smith/templates/etc/dnsmasq.conf/25NameServers |grep strict
# with each server strictly in the order they appear in
strict-order
Which makes it’s different then the default /etc/resolv.conf behavier.
Running the next will force dnsmasq to work as expected from the OS and to run queries against all DNS servers even if one fails.
echo "all-servers" > /etc/e-smith/templates-custom/etc/dnsmasq.conf/91_all-server
signal-event nethserver-dnsmasq-update
systemctl restart dnsmasq
It appears that also in other routers and devices this same config makes this issue a major one.
How do I mark it as resolved?
Also can we make a change from “strict-order” to “all-servers” as default to ovoid such issues in the future?
Thanks,
Eliezer