From 715c32f0fc0005dd39019e86c49f6dc00007c48d Mon Sep 17 00:00:00 2001 From: petercooperjr Date: Tue, 24 Nov 2020 19:38:14 -0500 Subject: [PATCH] Change example forwarding rule to match recommended .home.arpa TLD (#1523) The ".home" TLD was proposed at one point, and while it's probably not going to actually ever get delegated it's not best practice to just start using your own TLD. The .home.arpa domain has been specifically set aside for use in home networks (RFC 8375) and is probably the better example to put here. --- dnscrypt-proxy/example-forwarding-rules.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dnscrypt-proxy/example-forwarding-rules.txt b/dnscrypt-proxy/example-forwarding-rules.txt index 97a4859e..4c6497ae 100644 --- a/dnscrypt-proxy/example-forwarding-rules.txt +++ b/dnscrypt-proxy/example-forwarding-rules.txt @@ -13,10 +13,10 @@ ## Blocking IPv6 may prevent local devices from being discovered. ## If this happens, set `block_ipv6` to `false` in the main config file. -## Forward *.lan, *.local, *.home, *.internal and *.localdomain to 192.168.1.1 +## Forward *.lan, *.local, *.home.arpa, *.internal and *.localdomain to 192.168.1.1 # lan 192.168.1.1 # local 192.168.1.1 -# home 192.168.1.1 +# home.arpa 192.168.1.1 # internal 192.168.1.1 # localdomain 192.168.1.1