friert bei löschen rewrite Eintrag

[gitukrop]

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 or ask for help

• I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

Installation

Docker

Setup

On one machine

AdGuard Home version

services: adguardhome: image: adguard/adguardhome:latest container_name: adguardhome restart: unless-stopped

Action

Server: 192.168.0.129
Address: 192.168.0.129#53

---

QUESTIONS:
adguard.lan, type = A, class = IN
ANSWERS:
->  adguard.lan
internet address = 192.168.0.131
ttl = 10
AUTHORITY RECORDS:
ADDITIONAL RECORDS:

---

Non-authoritative answer:
Name: adguard.lan
Address: 192.168.0.131

Expected result

grüne kreis Inder Mitte

Actual result

dns rewrite loading andere dashboard angezeigt

Additional information and/or screenshots

nas dxp2800 UGOSPro

[tjharman]

I'm very sorry - I can't understand what you're saying the issue is. AdGuardHome freezes? Can you share screenshots?

Google Translate:

Es tut mir sehr leid – ich verstehe nicht, worin genau das Problem besteht. Friert AdGuardHome ein? Könnten Sie Screenshots teilen?

[gitukrop]

Danke der Grund war einen gelöschten docker container, der über caddy angesprochen wurde ..jetzt ist alles ok

…

Am 29.01.2026 um 20:02 schrieb Tim Harman ***@***.***>: tjharman left a comment (AdguardTeam/AdGuardHome#8213) <#8213 (comment)> I'm very sorry - I can't understand what you're saying the issue is. AdGuardHome freezes? Can you share screenshots? Google Translate: Es tut mir sehr leid – ich verstehe nicht, worin genau das Problem besteht. Friert AdGuardHome ein? Könnten Sie Screenshots teilen? — Reply to this email directly, view it on GitHub <#8213 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B3PQHLJ4W7R4ROQI7QH567T4JJKLXAVCNFSM6AAAAACSR5NEDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMJZG4YDKMRYGY>. You are receiving this because you authored the thread.

[gitukrop]

Setup Overview: DNS: AdGuard is running as the DNS server for the network. Reverse Proxy: Caddy is used as a reverse proxy for Docker applications. Docker Networking: Several Docker apps are assigned static IPs within a macvlan network using the range 192.168.0.128/27. This allows them to appear as regular devices on the LAN. Hostname Resolution: Hostnames matching *.lan are defined in AdGuard and forwarded to Caddy. Caddy then routes requests to the corresponding Docker app via its IPv4 address. Observed Issue: Accessing a corrupted Docker app caused AdGuard to freeze. The client experienced an hourglass/wait cursor during DNS resolution due to the faulty app Deleting the related block in Caddy restored normal operation. Notes: All services are internal and limited to the intranet. The issue appears to be related to how Caddy handled the routing for the corrupted app, which affected DNS resolution through AdGuard. Vielen Dank

…

Am 29.01.2026 um 20:02 schrieb Tim Harman ***@***.***>: tjharman left a comment (AdguardTeam/AdGuardHome#8213) <#8213 (comment)> I'm very sorry - I can't understand what you're saying the issue is. AdGuardHome freezes? Can you share screenshots? Google Translate: Es tut mir sehr leid – ich verstehe nicht, worin genau das Problem besteht. Friert AdGuardHome ein? Könnten Sie Screenshots teilen? — Reply to this email directly, view it on GitHub <#8213 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B3PQHLJ4W7R4ROQI7QH567T4JJKLXAVCNFSM6AAAAACSR5NEDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMJZG4YDKMRYGY>. You are receiving this because you authored the thread.