starred/AdGuardHome

Fork 0

mirror of https://github.com/AdguardTeam/AdGuardHome.git synced 2026-03-04 00:01:12 -05:00

AdGuardHome keep trying to use `[::1]:5353` to resolve domain. #5896

New issue

Closed

opened 2026-03-04 06:42:58 -05:00 by deekerman · 0 comments

deekerman commented

2026-03-04 06:42:58 -05:00

Owner

Originally created by @fernvenue on GitHub (Feb 3, 2026).

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

GitHub releases or script from README

Setup

Other (please mention in the description)

AdGuard Home version

v0.107.71

Action

AdGuardHome’s self-update check fails, and updating the block lists also fails. Checking the backend logs shows that AdGuardHome is attempting to resolve via [::1]:5353 instead of the system-defined DNS servers. This issue occurs when AdGuardHome tries to handle services related to itself, while AdGuardHome continues to use the DNS server configuration in its AdGuardHome.yaml when resolving user requests. I am certain that the system DNS is not [::1]:5353, nor is it using services such as systemd-resolved, and other services are working normally.

Expected result

AdGuardHome should respect and use the system DNS instead of trying to use [::1]:5353 for resolution.

Actual result

AdGuardHome actually always tries to use [::1]:5353 for resolution.

Additional information and/or screenshots

Realted logs:

...[info] webapi: warning: http error host=...com method=POST raddr=[::1]:47286 request_uri=/control/version.json status=502 err="getting version info: requesting https://static.adtidy.org/adguardhome/release/version.json: Get \"https://static.adtidy.org/adguardhome/release/version.json\": resolving \"static.adtidy.org\": exchanging with [::1]:5353 over udp: read udp [::1]:35000->[::1]:5353: read: connection refused\nexchanging with [::1]:5353 over udp: read udp [::1]:51245->[::1]:5353: read: connection refused"

And:

~# nslookup google.com
Server:		101.6.6.6
Address:	101.6.6.6#53

Non-authoritative answer:
Name:	google.com
Address: 142.250.196.206
Name:	google.com
Address: 2404:6800:4012:6::200e

~# cat /etc/resolv.conf 
nameserver 101.6.6.6

Originally created by @fernvenue on GitHub (Feb 3, 2026). ### 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) Linux, AMD64 (aka x86_64) ### Installation GitHub releases or script from README ### Setup Other (please mention in the description) ### AdGuard Home version v0.107.71 ### Action AdGuardHome’s self-update check fails, and updating the block lists also fails. Checking the backend logs shows that AdGuardHome is attempting to resolve via `[::1]:5353` instead of the system-defined DNS servers. This issue occurs when AdGuardHome tries to handle services related to itself, while AdGuardHome continues to use the DNS server configuration in its `AdGuardHome.yaml` when resolving user requests. I am certain that the system DNS is not `[::1]:5353`, nor is it using services such as `systemd-resolved`, and other services are working normally. ### Expected result AdGuardHome should respect and use the system DNS instead of trying to use `[::1]:5353` for resolution. ### Actual result AdGuardHome actually always tries to use `[::1]:5353` for resolution. ### Additional information and/or screenshots Realted logs: ``` ...[info] webapi: warning: http error host=...com method=POST raddr=[::1]:47286 request_uri=/control/version.json status=502 err="getting version info: requesting https://static.adtidy.org/adguardhome/release/version.json: Get \"https://static.adtidy.org/adguardhome/release/version.json\": resolving \"static.adtidy.org\": exchanging with [::1]:5353 over udp: read udp [::1]:35000->[::1]:5353: read: connection refused\nexchanging with [::1]:5353 over udp: read udp [::1]:51245->[::1]:5353: read: connection refused" ``` And: ``` ~# nslookup google.com Server: 101.6.6.6 Address: 101.6.6.6#53 Non-authoritative answer: Name: google.com Address: 142.250.196.206 Name: google.com Address: 2404:6800:4012:6::200e ~# cat /etc/resolv.conf nameserver 101.6.6.6 ```

deekerman closed this issue

2026-03-04 06:43:11 -05:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/AdGuardHome#5896

No description provided.

Rows
Columns

AdGuardHome keep trying to use [::1]:5353 to resolve domain. #5896