Conversation
|
In |
ainar-g
left a comment
There was a problem hiding this comment.
docs/adguard-home/encryption.md:127:235 MD059/descriptive-link-text Link text should be descriptive [Context: "[here]"]
docs/adguard-home/encryption.md:147:442 MD059/descriptive-link-text Link text should be descriptive [Context: "[here]"]
docs/adguard-home/encryption.md:200:36 MD059/descriptive-link-text Link text should be descriptive [Context: "[here]"]
docs/adguard-home/encryption.md:200:63 MD059/descriptive-link-text Link text should be descriptive [Context: "[here]"]
docs/adguard-home/encryption.md
Outdated
|
|
||
| ::: | ||
|
|
||
| This guide explains how to setup a "Secure DNS" server with AdGuard Home. |
There was a problem hiding this comment.
I'd replace "Secure DNS" with encrypted DNS without the quotation marks.
docs/adguard-home/encryption.md
Outdated
|
|
||
| ### Android | ||
|
|
||
| - Android 9 supports `DNS-over-TLS` natively. To configure it, go to *Settings* → *Network & internet* → *Advanced* → *Private DNS* and enter your domain name there. |
docs/adguard-home/encryption.md
Outdated
|
|
||
| ### iOS | ||
|
|
||
| - iOS 14 and higher support `DNS-over-TLS` and `DNS-over-HTTPS` natively via configuration profiles. In order to make things easier, AdGuard Home can generate these configuration profiles for you. Just head to *Setup Guide* → *DNS Privacy* and scroll to iOS. |
docs/adguard-home/encryption.md
Outdated
|
|
||
| ## Configuring DNSCrypt {#configure-dnscrypt} | ||
|
|
||
| Since v0.105.0, AdGuard Home is able to work as a DNSCrypt server. However, this feature is only available via configuration file, and can't be set up using the Web UI. This guide explains how to do this. |
There was a problem hiding this comment.
I don't think that mention of the version is necessary anymore.
docs/adguard-home/encryption.md
Outdated
|
|
||
| Here is how to generate a DNSCrypt configuration file and point AdGuard Home to it: | ||
|
|
||
| 1. :::info Important |
There was a problem hiding this comment.
Weird list. Perhaps, leave the Info outside of the list?
|
Preview was deployed to: https://pull-request-401.kb-dns.pages.dev/ |
docs/adguard-home/encryption.md
Outdated
|
|
||
| :::note | ||
|
|
||
| AdGuard Home also supports [DNSCrypt][dnscrypt-info] (both client-side and server-side). See [this section](#configure-dnscrypt) to learn about configuring AdGuard Home as a DNSCrypt server. |
There was a problem hiding this comment.
| AdGuard Home also supports [DNSCrypt][dnscrypt-info] (both client-side and server-side). See [this section](#configure-dnscrypt) to learn about configuring AdGuard Home as a DNSCrypt server. | |
| AdGuard Home supports both client-side and server-side [DNSCrypt][dnscrypt-info]. [Learn how to configure AdGuard Home as a DNSCrypt server](#configure-dnscrypt). |
docs/adguard-home/encryption.md
Outdated
|
|
||
| ## Server installation {#server-installation} | ||
|
|
||
| The purpose of securing the DNS traffic is to secure it from third-parties that might be analyzing or modifying it, e.g. from ISP. |
There was a problem hiding this comment.
| The purpose of securing the DNS traffic is to secure it from third-parties that might be analyzing or modifying it, e.g. from ISP. | |
| The purpose of securing the DNS traffic is to secure it from third parties that might be analyzing or modifying it, e.g., from ISP. |
docs/adguard-home/encryption.md
Outdated
|
|
||
| ## Get an SSL certificate {#certificate} | ||
|
|
||
| Both `DNS-over-HTTPS` and `DNS-over-TLS` are based on [TLS encryption][tls-wikipedia] so in order to use them, you will need to acquire an SSL certificate. |
There was a problem hiding this comment.
| Both `DNS-over-HTTPS` and `DNS-over-TLS` are based on [TLS encryption][tls-wikipedia] so in order to use them, you will need to acquire an SSL certificate. | |
| Both `DNS-over-HTTPS` and `DNS-over-TLS` are based on [TLS encryption][tls-wikipedia], so you will need an SSL certificate to use them. |
docs/adguard-home/encryption.md
Outdated
|
|
||
| Both `DNS-over-HTTPS` and `DNS-over-TLS` are based on [TLS encryption][tls-wikipedia] so in order to use them, you will need to acquire an SSL certificate. | ||
|
|
||
| An SSL certificate can be bought from a "Certificate Authority" (CA), a company trusted by browsers and operating systems to enroll SSL certificates for domains. |
There was a problem hiding this comment.
| An SSL certificate can be bought from a "Certificate Authority" (CA), a company trusted by browsers and operating systems to enroll SSL certificates for domains. | |
| An SSL certificate can be bought from a Certificate Authority (CA), a company trusted by browsers and operating systems to enroll SSL certificates for domains. |
docs/adguard-home/encryption.md
Outdated
|
|
||
| An SSL certificate can be bought from a "Certificate Authority" (CA), a company trusted by browsers and operating systems to enroll SSL certificates for domains. | ||
|
|
||
| Alternatively, you can get the certificate for free from ["Let's Encrypt" CA][letsencrypt], a free certificate authority developed by the Internet Security Research Group (ISRG). |
There was a problem hiding this comment.
| Alternatively, you can get the certificate for free from ["Let's Encrypt" CA][letsencrypt], a free certificate authority developed by the Internet Security Research Group (ISRG). | |
| Alternatively, you can get the certificate for free from the [Let’s Encrypt CA][letsencrypt], a free certificate authority developed by the Internet Security Research Group (ISRG). |
docs/adguard-home/encryption.md
Outdated
| There's also a really nice and easy-to-use alternative to CertBot called [LEGO][lego-source]. | ||
|
|
||
| 1. Install it using [an appropriate method][lego-install]. | ||
| 1. Choose your DNS provider from [the list][lego-provider] and follow the instruction to obtain a certificate. |
There was a problem hiding this comment.
| 1. Choose your DNS provider from [the list][lego-provider] and follow the instruction to obtain a certificate. | |
| 1. Choose your DNS provider from [the list][lego-provider] and follow the instructions to obtain a certificate. |
docs/adguard-home/encryption.md
Outdated
| 1. Install it using [an appropriate method][lego-install]. | ||
| 1. Choose your DNS provider from [the list][lego-provider] and follow the instruction to obtain a certificate. | ||
|
|
||
| Also, here's [a simple script][legoagh] that you can use to automate certificates generation and renewal. |
There was a problem hiding this comment.
| Also, here's [a simple script][legoagh] that you can use to automate certificates generation and renewal. | |
| Also, here’s [a simple script][legoagh] that you can use to automate certificates generation and renewal. |
docs/adguard-home/encryption.md
Outdated
|
|
||
| :::note | ||
|
|
||
| If a certificate and/or a private key is specified by file path, AdGuard Home will automatically reload them when they change. The reload may also be triggered by a SIGHUP signal. |
There was a problem hiding this comment.
| If a certificate and/or a private key is specified by file path, AdGuard Home will automatically reload them when they change. The reload may also be triggered by a SIGHUP signal. | |
| AdGuard Home will automatically reload certificates and/or private keys specified by file path when they change. A reload may also be triggered by a SIGHUP signal. |
docs/adguard-home/encryption.md
Outdated
|
|
||
| We already have a [guide][reverse-proxy-faq] on configuring a reverse proxy server for accessing AdGuard Home web UI. | ||
|
|
||
| AdGuard Home is able to restrict DNS-over-HTTPS requests which came from the proxy server not included into "trusted" list. By default, it's configured to accept requests from IPv4 and IPv6 loopback addresses. |
There was a problem hiding this comment.
please use quote marks and apostrophes according to our editorial policy
docs/adguard-home/encryption.md
Outdated
|
|
||
| :::note | ||
|
|
||
| Enter the host with your custom port! |
There was a problem hiding this comment.
| Enter the host with your custom port! | |
| Enter the host with your custom port. |
|
Preview was deployed to: https://pull-request-401.kb-dns.pages.dev/ |
Moving pages from wiki.