Update translations

i18n/cs/code.json

@@ -1,10 +1,10 @@
 {
   "siteConfig.title": {
-    "message": "AdGuard DNS Knowledge Base",
+    "message": "Databáze znalostí AdGuard DNS",
     "description": "The site title used in the browser tab and metadata"
   },
   "siteConfig.tagline": {
-    "message": "Knowledge base for AdGuard DNS",
+    "message": "Databáze znalostí pro AdGuard DNS",
     "description": "The site tagline used in meta description"
   },
   "theme.NotFound.title": {

i18n/cs/docusaurus-plugin-content-docs/current/adguard-home/clients.md

@@ -0,0 +1,125 @@
+---
+title: Clients
+sidebar_position: 7
+---
+
+AdGuard Home offers flexible configuration options for connected devices. At the most basic level, you may simply want to distinguish between them and see friendly names instead of IP addresses. AdGuard Home also allows you to apply different rules depending on the client.
+
+## Friendly names {#friendly-names}
+
+AdGuard Home tries to automatically collect some basic information about the device that’s connecting to it.
+
+Here is what it tries to do in order to figure out the client’s hostname:
+
+1. Inspects the hosts files (for example, `/etc/hosts`) and uses hostnames found there to identify clients.
+
+2. Makes reverse DNS lookups.
+
+3. Inspects the system ARP table.
+
+4. For public IP addresses, it also makes [WHOIS][whois] queries in order to find out the client’s location and the company the IP belongs to.
+
+5. For IP addresses leased by AdGuard Home’s DHCP server, it obtains the hostname from leases.
+
+If you only need to see friendly names in the AdGuard Home stats, editing the hosts file is probably the easiest way to achieve this. Please note that you may need to restart AdGuard Home to apply the changes.
+
+<!-- TODO(m.kazantsev): Host all screenshots from CDN.-->
+
+![top clients names](../../static/img/top-clients-names.png)
+
+Runtime clients sources can be disabled via the [`clients.runtime_sources`][sources] object of the configuration file.
+
+[whois]: https://en.wikipedia.org/wiki/WHOIS
+
+<!-- TODO(m.kazantsev): Update the reference, when the configuration is moved to the Knowledge Base.-->
+
+[sources]: https://github.com/AdguardTeam/AdGuardHome/wiki/Configuration#configuration-file
+
+## Persistent clients {#persistent-clients}
+
+If you want more than just the client names, you will need to configure each client manually. To do so, go to _Settings_ → _Client settings_ and click _Add client_.
+
+![new client](../../static/img/new-client.png)
+
+### Identifying clients {#identifying-clients}
+
+<!-- TODO(m.kazantsev): When the DHCP server article is moved, add a link to this article.-->
+
+First of all, you need to decide how you would like to identify the client. There are several options to do this.
+
+1. **IP address.** For instance, `192.168.0.1`. This is the easiest way to do this, but it may be not good enough if the IP address changes too often.
+
+2. **CIDR range.** For instance, `192.168.0.1/24`. It allows attributing a whole range of IP addresses (in this example, `192.168.0.*`) to the same client.
+
+3. **MAC address.** Using MAC as a client identifier is **only** possible when AdGuard Home works as the network’s DHCP server.
+
+4. **ClientIDs.** Special identifiers that can be used with some encrypted DNS protocols. [See below](#client-id).
+
+#### ClientID {#client-id}
+
+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, clients should perform queries using a special domain name or URL. Např:
+
+- AdGuard Home has the domain name `example.org`.
+
+- In AdGuard Home, add a persistent client with the ClientID `my-client`.
+
+- On the client device, you can now configure the following:
+
+  :::note
+
+  The URL ClientID has higher priority than the server-name ClientID. If you use both, only the URL ClientID is used.
+
+  :::
+
+  - **DNS-over-HTTPS:**
+
+    - URL ClientID: `https://example.org/dns-query/my-client`.
+
+    - Server-name ClientID: `https://my-client.example.org/dns-query` (requires a [wildcard certificate][wild]).
+
+  - **DNS-over-QUIC:** `quic://my-client.example.org` (requires a [wildcard 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** `example.org`.
+
+[wild]: https://en.wikipedia.org/wiki/Wildcard_certificate
+
+### Settings {#settings}
+
+Each client can be configured individually. You may choose what to block, what settings should be used, or you could even configure a completely different set of upstream DNS servers to be used for this client.
+
+![client settings](../../static/img/client-settings.png)
+
+## Per-client blocking {#per-client-blocking}
+
+There are two ways of how you can configure blocking on the per-client basis. Both of them are based on using AdGuard blocklist rules syntax for the rules you’re adding to _Custom filtering rules_.
+
+### `client` rules {#client-rules}
+
+The first method uses the `client` modifier. It allows you to limit the rule to a specific client or clients.
+
+Příklad:
+
+- `@@||*^$client=127.0.0.1`: Unblock everything for localhost.
+
+- `||example.org^$client='Frank\'s laptop'`: Block `example.org` for the client named `Frank's laptop` only. Note that quote (`'`) in the name must be escaped.
+
+- `||example.org^$client=192.168.0.0/24`: Block `example.org` for all clients with the IP addresses in the range `192.168.0.0-192.168.0.255`.
+
+You can find more `client` examples in the [article about the filtering rules syntax][filtering-syntax-client].
+
+### `ctag` rules {#ctag-rules}
+
+The second way is to use another modifier called `ctag`. When you create a new client, tags can be assigned to it. These tags can then be used in the filtering rules.
+
+Příklad:
+
+- `||example.org^$ctag=device_pc|device_phone`: Block `example.org` for clients tagged as `device_pc` or `device_phone`.
+
+- `||example.org^$ctag=~device_phone`: Block `example.org` for all clients except those tagged as `device_phone`.
+
+You can find more `ctag` examples as well as the full list of tags in the [article about the filtering rules syntax][filtering-syntax-ctag].
+
+[filtering-syntax-client]: /general/dns-filtering-syntax.md#client-modifier
+[filtering-syntax-ctag]: /general/dns-filtering-syntax.md#ctag-modifier