From 7311264e63d8c113c87720223e4e049e91edcdc6 Mon Sep 17 00:00:00 2001 From: Ainar Garipov Date: Fri, 26 Mar 2021 13:00:46 +0300 Subject: [PATCH] Pull request: DHCP: upd Merge in DNS/adguard-home-wiki from 2393-autohost-dhcp to master Squashed commit of the following: commit c51f778f1bfca1aca777a1eb09a89519a481d002 Author: Ainar Garipov Date: Fri Mar 26 13:00:14 2021 +0300 DHCP: imp commit 620085f8c39023ab0306bf72233d7f7180df82a0 Author: Ainar Garipov Date: Fri Mar 26 12:58:40 2021 +0300 DHCP: upd --- DHCP.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/DHCP.md b/DHCP.md index e40f227..8251188 100644 --- a/DHCP.md +++ b/DHCP.md @@ -110,12 +110,11 @@ the clients to choose between SLAAC and DHCPv6. ## Automatic Hosts -You can reach machines in the network more easily using the hostnames they send -in the DHCP requests with the `.lan` top-level domain. For example, if you have -a machine called “workstation” in the network, and it sends a DHCP request with -option 12 set to `workstation`, you can reach it over HTTP on the host -`http://workstation.lan`. +Machines in the network can be reached more easily using the hostnames they send +in the DHCP requests with a configurable top-level domain (TLD). By default, +the TLD is `lan`. For example, if you have a machine called “workstation” in +the network, and it sends a DHCP request with option 12 set to `workstation`, +you can reach it over HTTP on the host `http://workstation.lan`. -Configuring custom TLDs instead of the `.lan` one is planned, see issue [#2393]. - -[#2393]: https://github.com/AdguardTeam/AdGuardHome/issues/2393 +You can also set a custom TLD using the `dns.autohost_tld` field in the +[configuration] file.