summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXiao Pan <xyz@flylightning.xyz>2025-08-02 12:59:41 +0000
committerXiao Pan <xyz@flylightning.xyz>2025-08-02 12:59:41 +0000
commitc6cdb9387bcccbab6a24995334902894762b4623 (patch)
tree28df1bd4af5d3c066aef5f36578b8ef3526abe6b
parentf2bf4a854345a7061206bbaccedb1d5c0de79e27 (diff)
dnsmasq use many servers and ignore resolv.conf
man dnsmasq wrote "By default, dnsmasq will send queries to any of the upstream servers it knows about and tries to favour servers that are known to be up." There's a --strict-order option to make bottom server=... as highest priority, see [this stackexchange question][0]. I think this default behavior seems not very good, it send some unnecessary dns queries. But tcpdump shows there's not much dns query going on any way so maybe not a problem. [0]: https://unix.stackexchange.com/q/500900
-rw-r--r--etc/dnsmasq.conf9
1 files changed, 8 insertions, 1 deletions
diff --git a/etc/dnsmasq.conf b/etc/dnsmasq.conf
index 63bf311b..743f55aa 100644
--- a/etc/dnsmasq.conf
+++ b/etc/dnsmasq.conf
@@ -55,7 +55,7 @@
# If you don't want dnsmasq to read /etc/resolv.conf or any other
# file, getting its servers from this file instead (see below), then
# uncomment this.
-#no-resolv
+no-resolv
# If you don't want dnsmasq to poll /etc/resolv.conf or other resolv
# files for changes and re-read them then uncomment this.
@@ -687,3 +687,10 @@
# This fixes a security hole. see CERT Vulnerability VU#598349
#dhcp-name-match=set:wpad-ignore,wpad
#dhcp-ignore-names=tag:wpad-ignore
+
+server=2001:4860:4860::8888
+server=2606:4700:4700::1111
+server=2620:fe::9
+server=8.8.8.8
+server=1.1.1.1
+server=9.9.9.9