DNS rewrite rule not applied for local domain in AdGuard Home

[feydreva]

Hi,

I'm experiencing an issue with DNS rewrites not being applied in AdGuard Home (running in Docker).

I have configured several DNS rewrite rules in the AdGuard UI, for example:

• portainer.home.paradize.io → 10.0.0.112
• traefik.home.paradize.io → 10.0.0.112

However, when I query AdGuard directly, I still receive the public IP instead of the rewritten local IP.

Here's an example test:

feydreva@portainer:~$ dig portainer.home.paradize.io @10.0.0.112

; <<>> DiG 9.18.30-0ubuntu0.24.04.2-Ubuntu <<>> portainer.home.paradize.io @10.0.0.112
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1326
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;portainer.home.paradize.io. IN A

;; ANSWER SECTION:
portainer.home.paradize.io. 43172 IN A 82.66.8.184

I checked the Query Log, and the request is processed by AdGuard, but the rewrite rule doesn't seem to be applied.

I’ve already tried:

• Restarting AdGuard
• Clearing the DNS cache
• Deleting and re-adding the rewrite rule
• Ensuring AdGuard is listening on all interfaces (* on port 53)
• Verifying AdGuard is the actual DNS responder with ss -tulpen

What could cause AdGuard Home to ignore the rewrite?

Thanks in advance for your help!

[truthsword]

This is happening to me as well. When I use NSLOOKUP, the result comes from Cloudflare (1.1.1.1). The Rewrite is ignored.