Regarding the custom filter domain name and IP binding in the filter does not take effect

[GogogogoDAI]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to report a bug and not ask a question

Operating system type

Linux, Other (please mention the version in the description)

CPU architecture

64-bit ARM

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.108.0-b.22

Description

Including the current version has always had this problem
The custom filter domain name binding IP address in the filter does not take effect
The DNS rewrite binding domain name and IP in the filter can be used normally.

[ainar-g]

Hello and apologies for the late response. Could you show exactly which rule you're adding and how you're checking it? For example, a dig or an nslookup command.

[GogogogoDAI]

[ainar-g]

You've mentioned in the original post that your AGH is installed onto a Linux system, but the nslookup screenshot looks like it is from a Windows system, which queries 127.1.1.1, which is a local address. If AdGuard Home is installed on another system, please make sure that you've set up your Windows client correctly.

Also make sure that your Blocking mode is set to Default.

[GogogogoDAI]

Yes, I installed the trial program on the windows system and found that the specified ip still cannot be resolved, ip 127.1.1.1 is the adguardhome address, and the blocked address is 127.10.0.0

[ainar-g]

If your Blocking mode is set to Custom IP and that custom IP is 127.10.0.0 then everything is working as expected. If you want to have other IP addresses for these domain names, use the newer and better supported dnsrewrite rules:

|test.com$dnsrewrite=NOERROR;A;0.0.0.0,dnstype=A

[GogogogoDAI]

Thank you very much for solving my problem, but can you add a mode to use the custom interception ip and the default mode using the /etc/hosts function together?

[ainar-g]

I don't think that the support for the /etc/hosts format will expand. We seriously encourage using the more powerful dnsrewrite rules for these types of rewrites.

I'll close this issue, as everything seems to work as intended.