Random DNS timeout errors #13

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

Originally created by @ameshkov on GitHub (Jul 27, 2016).

Originally assigned to: @nkartyshov on GitHub.

$ nslookup lenta.ru 176.103.130.130
;; connection timed out; no servers could be reached

At the same time it resolves blocked domain:

$ nslookup ad.doubleclick.net 176.103.130.130
Server:     176.103.130.130
Address:    176.103.130.130#53

Non-authoritative answer:
Name:   ad.doubleclick.NET
Address: 127.0.0.1
Originally created by @ameshkov on GitHub (Jul 27, 2016). Originally assigned to: @nkartyshov on GitHub. ``` $ nslookup lenta.ru 176.103.130.130 ;; connection timed out; no servers could be reached ``` At the same time it resolves blocked domain: ``` $ nslookup ad.doubleclick.net 176.103.130.130 Server: 176.103.130.130 Address: 176.103.130.130#53 Non-authoritative answer: Name: ad.doubleclick.NET Address: 127.0.0.1 ```
deekerman 2026-03-04 00:03:12 -05:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@nkartyshov commented on GitHub (Sep 9, 2016):

done

@nkartyshov commented on GitHub (Sep 9, 2016): done
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#13
No description provided.