From 5de9f0469e99751851fbbb548f744f1422026aea Mon Sep 17 00:00:00 2001 From: "A.Kasper" Date: Fri, 25 Aug 2017 23:04:32 +0200 Subject: [PATCH] Update dns-cache.rst: adding a best practices for setting the name 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. --- docs/features/dns-cache.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/features/dns-cache.rst b/docs/features/dns-cache.rst index 92be66f6..cb23b268 100644 --- a/docs/features/dns-cache.rst +++ b/docs/features/dns-cache.rst @@ -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 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 = { - name = 'nextnode', + name = 'nextnode.yourdomain.net', ip6 = '2001:db8:8::1', ip4 = '198.51.100.1', }