nils/gluon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

explain that not setting dns.servers makes no sense

Browse Source
This commit is contained in:
Ralf Jung 2017-11-24 16:06:25 +01:00
parent 87c741b45e
commit c1aa5ff0f0
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/features/dns-cache.rst
View File

@ -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 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 'cacheentries' in RAM. The 'servers' list will be used to resolve the received
DNS queries if the request cannot be answered from cache. DNS queries if the request cannot be answered from cache. If these settings do
If these settings do not exist, the cache is not intialized and RAM usage will not increase. 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 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 next-node IP address are placed in the dnsmasq configuration. This means that the content