Skip to content

rewritten domains are not added to ipset even if configured #8341

@Gowee

Description

@Gowee

Prerequisites

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    waiting for dataWaiting for users to provide more data.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions