Pull request: 3418-clientid-doh

Merge in DNS/adguard-home-wiki from 3418-clientid-doh to master

Squashed commit of the following:

commit 9423a501898e966fa28830f1b10bdac13d8462a7
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Wed Oct 5 18:10:38 2022 +0300

    Clients: doh clientid in srvname
Ainar Garipov 2022-10-05 18:19:23 +03:00
parent 3d2d3fa50f
commit ef0d16e7fd
1 changed files with 11 additions and 4 deletions

@ -79,7 +79,7 @@ There are several options to do this.
ClientIDs are identifiers that can be used with the following DNS protocols: ClientIDs are identifiers that can be used with the following DNS protocols:
DNS-over-HTTPS, DNS-over-TLS, and DNS-over-QUIC. To use this identifier, DNS-over-HTTPS, DNS-over-TLS, and DNS-over-QUIC. To use this identifier,
clients should perform queries using a special domain name. For example: clients should perform queries using a special domain name or URL. For example:
* AdGuard Home has the domain name `example.org`. * AdGuard Home has the domain name `example.org`.
@ -87,12 +87,19 @@ clients should perform queries using a special domain name. For example:
* On the client device you can now configure: * On the client device you can now configure:
* **DNS-over-HTTPS:** `https://example.org/dns-query/my-client`; * **DNS-over-HTTPS:** `https://example.org/dns-query/my-client`.
* **DNS-over-TLS:** `tls://my-client.example.org` (requires a [wildcard
certificate][wild]); **Since **v0.108.0-b.18:** `https://my-client.example.org/dns-query`
(requires a [wildcard certificate][wild]). **NOTE:** The URL ClientID
has higher priority than the server-name ClientID. If you use both,
only the URL ClientID is used.
* **DNS-over-QUIC:** `quic://my-client.example.org` (requires a [wildcard * **DNS-over-QUIC:** `quic://my-client.example.org` (requires a [wildcard
certificate][wild]). certificate][wild]).
* **DNS-over-TLS:** `tls://my-client.example.org` (requires a [wildcard
certificate][wild]).
Note that the TLS certificate must be valid **both** for `*.example.org` **and** Note that the TLS certificate must be valid **both** for `*.example.org` **and**
`example.org`. `example.org`.