Unblocking problem #680

Closed
opened 2026-03-04 00:43:23 -05:00 by deekerman · 1 comment
Owner

Originally created by @Onepamopa on GitHub (May 6, 2019).

Version 0.95-hotfix.

Unblocking a domain causes AdGuard to return "NXDOMAIN" instead of the normal record.
Tried restarting it - no help.

Custom filter:
@@||data.mistat.intl.xiaomi.com^$important

Query AdGuard:

nslookup data.mistat.intl.xiaomi.com 127.0.0.1

Server: 127.0.0.1
Address: 127.0.0.1#53
** server can't find data.mistat.intl.xiaomi.com: NXDOMAIN

Query ISP DNS:

nslookup data.mistat.intl.xiaomi.com

Server: 84.43.191.252
Address: 84.43.191.252#53

Non-authoritative answer:
Name: data.mistat.intl.xiaomi.com
Address: 161.117.94.82
Name: data.mistat.intl.xiaomi.com
Address: 161.117.97.84
Name: data.mistat.intl.xiaomi.com
Address: 161.117.71.89
Name: data.mistat.intl.xiaomi.com
Address: 161.117.96.220
Name: data.mistat.intl.xiaomi.com
Address: 161.117.71.92
Name: data.mistat.intl.xiaomi.com
Address: 161.117.97.83

Originally created by @Onepamopa on GitHub (May 6, 2019). Version 0.95-hotfix. Unblocking a domain causes AdGuard to return "NXDOMAIN" instead of the normal record. Tried restarting it - no help. Custom filter: @@||data.mistat.intl.xiaomi.com^$important Query AdGuard: # nslookup data.mistat.intl.xiaomi.com 127.0.0.1 Server: 127.0.0.1 Address: 127.0.0.1#53 ** server can't find data.mistat.intl.xiaomi.com: NXDOMAIN Query ISP DNS: # nslookup data.mistat.intl.xiaomi.com Server: 84.43.191.252 Address: 84.43.191.252#53 Non-authoritative answer: Name: data.mistat.intl.xiaomi.com Address: 161.117.94.82 Name: data.mistat.intl.xiaomi.com Address: 161.117.97.84 Name: data.mistat.intl.xiaomi.com Address: 161.117.71.89 Name: data.mistat.intl.xiaomi.com Address: 161.117.96.220 Name: data.mistat.intl.xiaomi.com Address: 161.117.71.92 Name: data.mistat.intl.xiaomi.com Address: 161.117.97.83
Author
Owner

@Onepamopa commented on GitHub (May 8, 2019):

I think that was actually related to the dns server currently in use (it was the adguard one).
Changed to cloudflare+google, no troubles.

@Onepamopa commented on GitHub (May 8, 2019): I think that was actually related to the dns server currently in use (it was the adguard one). Changed to cloudflare+google, no troubles.
Sign in to join this conversation.
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#680
No description provided.