From 89c1d8d668b8b48bacf2564a0f4fd763f82a5887 Mon Sep 17 00:00:00 2001 From: Simon Zolin Date: Thu, 27 Jun 2019 14:39:54 +0300 Subject: [PATCH 1/2] + Recursive DNS server --- Configuration.md | 1 + Unbound.md | 23 +++++++++++++++++++++++ 2 files changed, 24 insertions(+) create mode 100644 Unbound.md diff --git a/Configuration.md b/Configuration.md index 2047a9c..3233d3c 100644 --- a/Configuration.md +++ b/Configuration.md @@ -5,6 +5,7 @@ Most of these settings can be changed via the web-based admin interface. However * [Command-line arguments](#command-line) * [Configuring upstreams](#upstreams) * [Specifying upstreams for domains](#upstreams-for-domains) + * [Recursive DNS server](Unbound.md) * [Configuring clients friendly names](#friendly-names) * [Configuration file](#configuration-file) diff --git a/Unbound.md b/Unbound.md new file mode 100644 index 0000000..fb4d76b --- /dev/null +++ b/Unbound.md @@ -0,0 +1,23 @@ +# Recursive DNS server + +A recursive DNS server doesn't require an upstream server to resolve a domain name (e.g. `www.hostname.com`). Instead, it starts with Root DNS servers and then recursively asks authoritative DNS servers for each part of the domain name (e.g. `com`, then `hostname.com`). Finally, it reaches the specific authoritative server which is responsible for the target domain name (e.g. `www.hostname.com`). One such recursive DNS server is `unbound`. You can read more information about it here: https://nlnetlabs.nl/projects/unbound/about/. + +AdGuard Home can work with `unbound` on several system configurations (currently, Linux-amd64 and Linux-arm). + + +## Enable recursive DNS server + +To enable recursive DNS server, add `unbound` to the "Upstream DNS servers" list in UI. +If you want to use it for specific domains only, use `[/hostname/]unbound` setting. + + +## Configure libunbound + +libunbound has many configuration settings that you can set in `AdGuardHome.yaml` file. The list of supported settings is located here: https://nlnetlabs.nl/documentation/unbound/unbound.conf/ + +For example, to set libunbound cache size equal to 8 megabytes, use this setting: + + dns: + ... + unbound_settings: + - 'msg-cache-size: 8m' From c4f41d9a94bc3fd0136c88d43494a27bd9adc799 Mon Sep 17 00:00:00 2001 From: Simon Zolin Date: Mon, 1 Jul 2019 13:41:29 +0300 Subject: [PATCH 2/2] update description --- Unbound.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Unbound.md b/Unbound.md index fb4d76b..f4a1e85 100644 --- a/Unbound.md +++ b/Unbound.md @@ -2,7 +2,7 @@ A recursive DNS server doesn't require an upstream server to resolve a domain name (e.g. `www.hostname.com`). Instead, it starts with Root DNS servers and then recursively asks authoritative DNS servers for each part of the domain name (e.g. `com`, then `hostname.com`). Finally, it reaches the specific authoritative server which is responsible for the target domain name (e.g. `www.hostname.com`). One such recursive DNS server is `unbound`. You can read more information about it here: https://nlnetlabs.nl/projects/unbound/about/. -AdGuard Home can work with `unbound` on several system configurations (currently, Linux-amd64 and Linux-arm). +AdGuard Home can use a built-in unbound DNS recursor on several system configurations (currently, Linux-amd64 and Linux-arm). ## Enable recursive DNS server