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

Update dns-cache.rst: adding a best practices for setting the name

Browse Source 
Adding hints that the next_node name should contain a dot to avoid (mobile) browsers interpreting "nextnode" as searchphrase. Also setting it to an fqdn helps when clients use static dns servers.
This commit is contained in:
A.Kasper 2017-08-25 23:04:32 +02:00 committed by Christof Schulze
parent 9168107f13
commit 5de9f0469e
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

@ -21,7 +21,10 @@ If these settings do not exist, the cache is not intialized and RAM usage will n
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
of next_node.name may be resolved even without upstream connectivity. of next_node.name may be resolved even without upstream connectivity. It is suggested to use
the same name as the DNS server provides: e.g nextnode.yourdomain.net (This way the name also
works if client uses static DNS Servers). Hint: If next_node.name does not contain a dot some
browsers would open the searchpage instead.
:: ::
@ -31,7 +34,7 @@ of next_node.name may be resolved even without upstream connectivity.
}, },
next_node = { next_node = {
name = 'nextnode', name = 'nextnode.yourdomain.net',
ip6 = '2001:db8:8::1', ip6 = '2001:db8:8::1',
ip4 = '198.51.100.1', ip4 = '198.51.100.1',
} }