Does AdGuard Home support IPv6 Blocking/Filtering?
I鈥檓 running AdGuard Home on a Pi. I鈥檝e added the IPv6 Cloudflare dns servers to the configuration, and they seem to pass the upstream test. I鈥檝e also added the Pi鈥檚 IPv6 address as the dns entry on my router configuration. So far I haven鈥檛 been able to get IPv6 blocking to work.
AdGuard Home does respond with NXDOMAIN for AAAA requests for blocked domains:
$ nslookup -query=AAAA doubleclick.net
Server: 192.168.7.2
Address: 192.168.7.2#53
** server can't find doubleclick.net: NXDOMAIN
So far I haven鈥檛 been able to get IPv6 blocking to work.
Could you please specify how did you test?
How come when I run it, I don't get NXDOMAIN but 127.0.0.1:

How come when I run it, I don't get NXDOMAIN but 127.0.0.1:
Oh, its because I had enabled the other filters:

If you only leave the first one on, you get NXDOMAIN. If I'm not mistaking, NXDOMAIN is faster than 127.0.0.1... Something to look into maybe?
If you only leave the first one on, you get NXDOMAIN. If I'm not mistaking, NXDOMAIN is faster than 127.0.0.1... Something to look into maybe?
If a domain is blocked by an adblock-syntax rule like ||example.org, AG Home returns NXDOMAIN.
If there's a matching host in one of the hosts files, AG Home returns the IP that's configured by the hosts file.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
If a domain is blocked by an adblock-syntax rule like
||example.org, AG Home returns NXDOMAIN.If there's a matching host in one of the hosts files, AG Home returns the IP that's configured by the hosts file.