AdguardTeam / AdguardTeam/AdGuardHome
rewritten domains are not added to ipset even if configured
- 主要言語
- TypeScript
- スター
- 36.9k
- フォーク
- 2.5k
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
### Prerequisites
- [x] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found no answer
- [x] I have searched other issues and found no duplicates
- [x] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)
- [x] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)
### Platform (OS and CPU architecture)
Custom (please mention in the description)
### Installation
Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)
### Setup
On a router, DHCP is handled by the router
### AdGuard Home version
v0.107.46
### Action
1. Set a custom DNS rewrite rule in ADG like `*.example.org -> 192.0.2.3`.
2. Set a matching ipset rule in ADG like `example.org/custom_set`.
3. Resolve the domain via ADG like `drill www.example.org @192.0.0.1`
### Expected result
`ipset list custom_set | grep 192.0.2.3` shows a match. That is, the resolved IP of the rewritten domain `www.example.org` is added to `custom_set` as expected.
### Actual result
`ipset list custom_set | grep 192.0.2.3` shows nothing. That is, the resolved IP of the rewritten domain `www.example.org` is not added to `custom_set`.
### Additional information and/or screenshots
OS: OpenWrt 5.15.162 (offcial build)
Package: `adguardhome - 0.107.46-1` (in official repo)
コントリビューションガイド
評価
この issue はまだ評価されていません。