From c1aa5ff0f051d162a3a2edf6f9d055a267c5e091 Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Fri, 24 Nov 2017 16:06:25 +0100 Subject: [PATCH] explain that not setting dns.servers makes no sense --- docs/features/dns-cache.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/features/dns-cache.rst b/docs/features/dns-cache.rst index cb23b268..4f9b583e 100644 --- a/docs/features/dns-cache.rst +++ b/docs/features/dns-cache.rst @@ -16,8 +16,11 @@ There are the following settings: If both options are set the node will cache as much DNS records as set with 'cacheentries' in RAM. The 'servers' list will be used to resolve the received -DNS queries if the request cannot be answered from cache. -If these settings do not exist, the cache is not intialized and RAM usage will not increase. +DNS queries if the request cannot be answered from cache. If these settings do +not exist, the cache is not intialized and RAM usage will not increase. Note +that not setting 'servers' here defeates the purpose; once the routers all +announce the "next node" address for DNS, there is no way for nodes to +automatically determine DNS servers. They have to be baked into the firmware. When next_node.name is set, an A record and an AAAA record for the next-node IP address are placed in the dnsmasq configuration. This means that the content