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

docs: features/dns-cache: clean up

Browse Source
This commit is contained in:
Matthias Schiffer 2017-06-07 17:07:52 +02:00
parent 8bfa3f96c9
commit 71bfa305fd
No known key found for this signature in database
GPG Key ID: 16EF3F64CB201D9C
1 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,9 +1,10 @@
DNS-Caching
DNS caching
===========
User experience may be greatly improved when dns is accelerated. Also, it
seems like a good idea to keep the number of packages being exchanged
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
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
@ -15,11 +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.
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
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
of next_node.name may be resolved even without upstream connectivity.
::