mirrors
/
AdGuardHome
mirror of https://github.com/AdguardTeam/AdGuardHome.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Pull request: Hosts-Blocklists: mention upstream bug 

Merge in DNS/adguard-home-wiki from ups-file to master

Squashed commit of the following:

commit ae5edb6af9d660f89adcf77a5551ddf2a7d917c8
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Mon Aug 9 21:22:12 2021 +0300

    Hosts-Blocklists: mention upstream bug
Ainar Garipov 2021-08-10 12:38:48 +03:00
parent 0986c8ccd2
commit 3d75334d43
2 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Configuration.md

@ -169,6 +169,11 @@ may want to load them from a separate file instead of setting all upstreams in
AdGuard Home settings. To do that, simply specify the path to a file with your AdGuard Home settings. To do that, simply specify the path to a file with your
list in the `upstream_dns_file` field of `AdGuardHome.yaml`. list in the `upstream_dns_file` field of `AdGuardHome.yaml`.
**BUG:** The file, just like the input in the web interface, currently doesn't
accept internationalized domain names (e.g. `пример.рф` or `例子.中国`). As
a workaround, convert them to Punycode (e.g. `xn--e1afmkfd.xn--p1ai` or
`xn--fsqu00a.xn--fiqs8s` respectively). See [issue 2915][2915].
### <a href="#upstreams-for-rdns" id="upstreams-for-rdns" name="upstreams-for-rdns">Specifying Upstreams For Reverse DNS</a> ### <a href="#upstreams-for-rdns" id="upstreams-for-rdns" name="upstreams-for-rdns">Specifying Upstreams For Reverse DNS</a>
Using the domain-specific upstream notation, you can specify dedicated upstream Using the domain-specific upstream notation, you can specify dedicated upstream
@ -249,6 +254,7 @@ Since **v0.106.0** you can enable and disable this feature with “Enable client
hostname resolution” setting in the “Upstream DNS servers” section or via the hostname resolution” setting in the “Upstream DNS servers” section or via the
`resolve_clients` field in the configuration file. `resolve_clients` field in the configuration file.
[2915]: https://github.com/AdguardTeam/AdGuardHome/issues/2915
[DNS Stamps]: https://dnscrypt.info/stamps/ [DNS Stamps]: https://dnscrypt.info/stamps/
[DNS-over-HTTPS]: https://en.wikipedia.org/wiki/DNS_over_HTTPS [DNS-over-HTTPS]: https://en.wikipedia.org/wiki/DNS_over_HTTPS
[DNS-over-QUIC]: https://datatracker.ietf.org/doc/html/draft-ietf-dprive-dnsoquic-03 [DNS-over-QUIC]: https://datatracker.ietf.org/doc/html/draft-ietf-dprive-dnsoquic-03

4
Hosts-Blocklists.md

@ -316,8 +316,8 @@ $dnstype=value2
* `||example.org^$dnstype=AAAA`: block DNS queries for the IPv6 addresses of * `||example.org^$dnstype=AAAA`: block DNS queries for the IPv6 addresses of
`example.org`. `example.org`.
* `||example.org^$dnstype=~A|~CNAME`: only allow `A` and `CNAME` DNS queries for * `||example.org^$dnstype=~A|~CNAME`: only allow `A` and `CNAME` DNS queries
`example.org`, block out the rest. for `example.org`, block out the rest.
#### <a href="#dnsrewrite" id="dnsrewrite" name="dnsrewrite">`dnsrewrite`</a> #### <a href="#dnsrewrite" id="dnsrewrite" name="dnsrewrite">`dnsrewrite`</a>