better upstream server description (#1106)
gluon-core: dns-cache documentation polish Now its clear that upstreams severs normally means "community gateways". * added cacheentries to description * made upstream server description more general * description of the A and AAAA-records for next_node added * mention of Cache not being allocated when not set in site.conf * dns-cache doku polish
This commit is contained in:
parent
6c053d92b8
commit
22042a3bf2
@ -6,11 +6,21 @@ 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. All settings are optional, though if no dns server is
|
added to site.conf. Upstream servers are the DNS servers which are normally
|
||||||
set, the configuration will not be altered by gluon-core.
|
used by the nodes to resolve hostnames (e.g. gateways/supernodes).
|
||||||
|
|
||||||
Besides caching dns requests from clients, the next_node-addresses are set to
|
There are the following settings:
|
||||||
resolve to a configurable name that may optionally be placed in next_node.name.
|
servers
|
||||||
|
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.
|
||||||
|
|
||||||
::
|
::
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user