AdGuardHome
AdGuardHome copied to clipboard
PTR queries for DHCP clients aren't being affected by filtering rules
Prerequisites
- [x] I am running the latest version
- [x] I checked the documentation and found no answer
- [ ] I checked to make sure that this issue has not already been filed
Issue Details
-
Version of AdGuard Home server:
- 0.106.3
-
How did you install AdGuard Home:
- Docker
-
How did you setup DNS configuration:
-
If it's a router or IoT, please write device model:
-
CPU architecture:
- arm64
-
Operating system and version:
- Ubuntu 20.04
Issue Details
I've created a rule that blocks PTR queries for my local network range.
![Screen Shot 2021-10-16 at 4 53 40 PM](https://user-images.githubusercontent.com/19761269/137585534-5408fb88-257a-4da2-98c6-2dac00dc62e4.png)
However, some queries are still being answered:
![Screen Shot 2021-10-16 at 4 54 50 PM](https://user-images.githubusercontent.com/19761269/137585558-f5b8921b-7594-4361-b911-fe71175fbffb.png)
Additional Information
Seems like it replies to queries when AGH is used as DHCP.
Hm. If I recall correctly, PTR queries for IPs within locally served networks are processed before most of the filtering takes place. @EugeneOne1, please confirm.
@ameshkov, do we need an ability to filter out certain PTR requests within the locally served network?
@ainar-g, yeah, all the PTR requests for private/local IPs (including DHCP leased) aren't filtered at all.
@ameshkov, ping?
Probably, but with a very low priority IMO