mirrors/AdGuardHome
1
0
Fork 0
mirror of https://github.com/AdguardTeam/AdGuardHome.git synced 2024-11-22 04:55:33 +03:00
Code Issues Projects Releases Packages Wiki Activity

Pull request: Hosts-Blocklists: mention dnstype change 

Merge in DNS/adguard-home-wiki from dnstype-change to master

Squashed commit of the following:

commit 775dd274eb06deb49ae8e03c368de2e3d376319a
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Tue Feb 8 16:30:00 2022 +0300

    Hosts-Blocklists: mention dnstype change
Ainar Garipov 2022-02-08 18:32:30 +03:00
parent aff71f7491
commit 9d5dda92bd
1 changed files with 24 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
Hosts-Blocklists.md

@ -295,8 +295,8 @@ how to solve this with `denyallow`:
Available since **v0.105.0**.
The `dnstype` modifier allows specifying DNS request type on which this rule
will be triggered.
The `dnstype` modifier allows specifying DNS request or response type on which
this rule will be triggered.
The syntax is:
@ -328,6 +328,28 @@ $dnstype=value2
* `||example.org^$dnstype=~A|~CNAME`: only allow `A` and `CNAME` DNS queries
for `example.org`, block out the rest.
**NOTE:** Before version **v0.108.0,** AdGuard Home would use the type of the
request to filter the response records, as opposed to the type of the response
record itself. That caused issues, since that meant that you could not write
rules that would allow certain `CNAME` records in responses in `A` and `AAAA`
requests. In **v0.108.0** that behaviour was changed, so now this:
```none
||canon.example.com^$dnstype=~CNAME
```
allows you to avoid filtering of the following response:
```none
ANSWERS:
-> example.com
canonical name = canon.example.com.
ttl = 60
-> canon.example.com
internet address = 1.2.3.4
ttl = 60
```
#### <a href="#dnsrewrite" id="dnsrewrite" name="dnsrewrite">`dnsrewrite`</a>
Available since **v0.105.0**.