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

Revert "better upstream server description (#1106)"

Browse Source 
This reverts commit 22042a3bf2.
This commit is contained in:
Christof Schulze 2017-04-27 09:07:28 +02:00
parent 373613bb54
commit ebdd72d877
1 changed files with 4 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -6,21 +6,11 @@ between node and gateway as small as possible. In order to do this, a
dns-cache may be used on a node. The dnsmasq instance listening on port dns-cache may be used on a node. The dnsmasq instance listening on port
53 on the node will be reconfigured to answer requests, use a list of 53 on the node will be reconfigured to answer requests, use a list of
upstream servers and a specific cache size if the options listed below are upstream servers and a specific cache size if the options listed below are
added to site.conf. Upstream servers are the DNS servers which are normally added to site.conf. All settings are optional, though if no dns server is
used by the nodes to resolve hostnames (e.g. gateways/supernodes). set, the configuration will not be altered by gluon-core.
There are the following settings: Besides caching dns requests from clients, the next_node-addresses are set to
servers resolve to a configurable name that may optionally be placed in next_node.name.
cacheentries
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.
When next_node.name is set, an A-record and an AAAA-record for the
next-node-IP are placed in the dnsmasq configuration. This means that the content
of next_node.name may be resolved even without upstream connectivity.
:: ::