From 32c99a2d437f54579d81bdd952ead83d39cb2945 Mon Sep 17 00:00:00 2001 From: Aminda Suomalainen Date: Wed, 1 May 2024 13:08:06 +0300 Subject: [PATCH] etc/resolv.conf: fix comment explaining rotate --- etc/resolv.conf | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/etc/resolv.conf b/etc/resolv.conf index 9a54d09d..4e7d086e 100644 --- a/etc/resolv.conf +++ b/etc/resolv.conf @@ -31,11 +31,16 @@ search . # timeout:2 = nameserver timeout 2 s (default 5, max 30), then next # attempts:2 = if all nameservers fail, attempt again 2 times (def 2, max 5) -# rotate = instead of trying the nameservers in the order specified, randomize -# the order in round-robin fashion. They are all theoretically the same, -# except that NordVPN disables IPv6 so ::1 will fail and occassionally only -# systemd-resolved works and I am under impression that some apps are aware of -# systemd-resolved and will use it directly bypassing resolv.conf +# rotate = For long running processes that perform more than one query (so not +# dig/host), use the first resolver for the first query, second resolver for +# the second query, third resolver for the third query and repeat. +# They are all theoretically the same, except that NordVPN disables IPv6 so +# ::1 will fail and occassionally only systemd-resolved works and I am +# under the impression that some apps are aware of systemd-resolved and will +# use it directly bypassing resolv.conf. In other words while everything +# works, this affects nothing, and when unbound is down (before it's started +# on desktop?), every second query will be faster with every third reaching +# systemd-resolved instantly without the timeout of two seconds. # edns0 = extended DNS # trust-ad = trust DNSSEC authenticated data options timeout:2 attempts:2 rotate edns0 trust-ad