v0.92 - sporadic DNS error #505

tomacco81 · 2018-12-31T10:45:25Z

Since v0.92 I'm getting sporadic DNS errors (Failed to read a request from 1.1.1.1:853, cause: EOF)

Steps to reproduce

host adguard.com 127.0.0.1

Expected behavior

Name: 127.0.0.1
Address: 127.0.0.1#53
Aliases: 

adguard.com has address 104.20.30.130
adguard.com has address 104.20.31.130
adguard.com has IPv6 address 2606:4700:10::6814:1e82
adguard.com has IPv6 address 2606:4700:10::6814:1f82
adguard.com mail is handled by 10 mx.yandex.net.

Actual behavior

Using domain server:
Name: 127.0.0.1
Address: 127.0.0.1#53
Aliases: 

Host adguard.com not found: 2(SERVFAIL)

Debug output:

2018/12/31 11:17:23 AdGuard Home web interface backend, version v0.92
2018/12/31 11:17:23 Current working directory is /home/pi/AdGuardHome
2018/12/31 11:17:23 config file /home/pi/AdGuardHome/AdGuardHome.yaml does not exist, nothing to upgrade
2018/12/31 11:17:23 Reading YAML file: /home/pi/AdGuardHome/AdGuardHome.yaml
2018/12/31 11:17:23 YAML file doesn't exist, skipping: /home/pi/AdGuardHome/AdGuardHome.yaml
2018/12/31 11:17:23 Loading filter 1 contents to: /home/pi/AdGuardHome/data/filters/1.txt
2018/12/31 11:17:23 Couldn't load filter 1 contents due to stat /home/pi/AdGuardHome/data/filters/1.txt: no such file or directory
2018/12/31 11:17:23 Downloading update for filter 1 from https://adguardteam.github.io/AdGuardSDNSFilter/Filters/filter.txt
2018/12/31 11:17:23 Filter 1 has been updated: 500197 bytes, 25936 rules
2018/12/31 11:17:23 Saving filter 1 contents to: /home/pi/AdGuardHome/data/filters/1.txt
2018/12/31 11:17:23 Writing YAML file: /home/pi/AdGuardHome/AdGuardHome.yaml
2018/12/31 11:17:23 Writing YAML file: /home/pi/AdGuardHome/AdGuardHome.yaml
2018/12/31 11:17:23 Creating dnsfilter
2018/12/31 11:17:24 Loading stats from querylog
2018/12/31 11:17:24 Starting the DNS proxy server
2018/12/31 11:17:24 Ratelimit is enabled and set to 20 rps
2018/12/31 11:17:24 The server is configured to refuse ANY requests
2018/12/31 11:17:24 DNS cache is enabled
2018/12/31 11:17:24 Creating the UDP server socket
2018/12/31 11:17:24 Listening to udp://[::]:53
2018/12/31 11:17:24 Go to http://127.0.0.1:3000
2018/12/31 11:17:24 Entering the UDP listener loop on [::]:53
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 127.0.0.1:33900
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 29190
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;github.com.    IN       A
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.0.0.1:853 (1)
upstream.(*TLSPool).Get(): Dialing to 1.0.0.1:853
proxy.(*Proxy).Resolve(): RTT: 322 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 29190
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;github.com.    IN       A

;; ANSWER SECTION:
github.com.     58      IN      A       192.30.253.112
github.com.     58      IN      A       192.30.253.113
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 127.0.0.1:47626
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 1348
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;github.com.    IN       AAAA
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:853 (0)
upstream.(*TLSPool).Get(): Dialing to 1.1.1.1:853
proxy.(*Proxy).Resolve(): RTT: 272 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 1348
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;github.com.    IN       AAAA

;; AUTHORITY SECTION:
github.com.     435     IN      SOA     ns-1707.awsdns-21.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 127.0.0.1:59009
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 27641
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;github.com.    IN       MX
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:853 (0)
upstream.(*TLSPool).Get(): Returning existing connection to 1.1.1.1:853
proxy.(*Proxy).Resolve(): RTT: 18 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 27641
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;github.com.    IN       MX

;; ANSWER SECTION:
github.com.     2550    IN      MX      5 alt1.aspmx.l.google.com.
github.com.     2550    IN      MX      5 alt2.aspmx.l.google.com.
github.com.     2550    IN      MX      10 alt3.aspmx.l.google.com.
github.com.     2550    IN      MX      10 alt4.aspmx.l.google.com.
github.com.     2550    IN      MX      1 aspmx.l.google.com.
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 127.0.0.1:51953
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 21781
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;adguard.com.   IN       A
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:853 (0)
upstream.(*TLSPool).Get(): Returning existing connection to 1.1.1.1:853
proxy.(*Proxy).Resolve(): RTT: 0 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: SERVFAIL, id: 21781
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;adguard.com.   IN       A
proxy.(*Proxy).handleUDPPacket(): error handling DNS (udp) request: talking to dnsUpstream failed, cause: Failed to read a request from 1.1.1.1:853, cause: EOF
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 127.0.0.1:58301
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 63958
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;adguard.com.   IN       A
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:853 (0)
upstream.(*TLSPool).Get(): Dialing to 1.1.1.1:853
proxy.(*Proxy).Resolve(): RTT: 313 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 63958
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;adguard.com.   IN       A

;; ANSWER SECTION:
adguard.com.    9       IN      A       104.20.30.130
adguard.com.    9       IN      A       104.20.31.130
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 127.0.0.1:51084
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 31321
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;adguard.com.   IN       AAAA
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:853 (0)
upstream.(*TLSPool).Get(): Returning existing connection to 1.1.1.1:853
proxy.(*Proxy).Resolve(): RTT: 22 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 31321
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;adguard.com.   IN       AAAA

;; ANSWER SECTION:
adguard.com.    9       IN      AAAA    2606:4700:10::6814:1e82
adguard.com.    9       IN      AAAA    2606:4700:10::6814:1f82
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 127.0.0.1:47365
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 53334
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;adguard.com.   IN       MX
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:853 (0)
upstream.(*TLSPool).Get(): Returning existing connection to 1.1.1.1:853
proxy.(*Proxy).Resolve(): RTT: 29 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 53334
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;adguard.com.   IN       MX

;; ANSWER SECTION:
adguard.com.    120     IN      MX      10 mx.yandex.net.
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 127.0.0.1:35731
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 42165
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.    IN       A
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:853 (0)
upstream.(*TLSPool).Get(): Returning existing connection to 1.1.1.1:853
proxy.(*Proxy).Resolve(): RTT: 0 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: SERVFAIL, id: 42165
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.    IN       A
proxy.(*Proxy).handleUDPPacket(): error handling DNS (udp) request: talking to dnsUpstream failed, cause: Failed to read a request from 1.1.1.1:853, cause: EOF
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 127.0.0.1:58581
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 61169
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.    IN       A
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:853 (0)
upstream.(*TLSPool).Get(): Dialing to 1.1.1.1:853
proxy.(*Proxy).Resolve(): RTT: 309 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 61169
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.    IN       A

;; ANSWER SECTION:
google.com.     61      IN      A       216.58.207.46
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 127.0.0.1:40590
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 7467
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.    IN       AAAA
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:853 (0)
upstream.(*TLSPool).Get(): Returning existing connection to 1.1.1.1:853
proxy.(*Proxy).Resolve(): RTT: 31 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 7467
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.    IN       AAAA

;; ANSWER SECTION:
google.com.     70      IN      AAAA    2a00:1450:4001:808::200e
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 127.0.0.1:48402
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 60335
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.    IN       MX
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:853 (0)
upstream.(*TLSPool).Get(): Returning existing connection to 1.1.1.1:853
proxy.(*Proxy).Resolve(): RTT: 37 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 60335
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.    IN       MX

;; ANSWER SECTION:
google.com.     232     IN      MX      10 aspmx.l.google.com.
google.com.     232     IN      MX      20 alt1.aspmx.l.google.com.
google.com.     232     IN      MX      30 alt2.aspmx.l.google.com.
google.com.     232     IN      MX      40 alt3.aspmx.l.google.com.
google.com.     232     IN      MX      50 alt4.aspmx.l.google.com.

Your environment

Description	Value
Version of AdGuard Home server:	v0.92
How did you setup DNS configuration:	IoT
If it's a router or IoT, please write device model:	Raspberry Pi 3 Model B Rev 1.2
Operating system and version:	Raspbian GNU/Linux 9 (stretch)

The text was updated successfully, but these errors were encountered:

uraimo · 2018-12-31T12:56:13Z

Same here, on a RaspberryPi Zero, latest Raspbian (6 ips in the upstream_dns list, cloudflare,quad9 and adguard).
Just I would describe it as "sporadic", since most of the times the dns resolution fails.

ameshkov · 2018-12-31T13:07:13Z

It happens when the tcp connection to the upstream is closed after some time. @hmage I guess we should re-connect automatically right away.

ameshkov · 2019-01-02T17:17:19Z

Temporary solution: use a DNSCrypt, DOH, or plain DNS upstream.

uraimo · 2019-01-02T17:26:00Z

Thanks @ameshkov.

Vansinnet · 2019-01-02T20:37:54Z

Temporary solution: use a DNSCrypt, DOH, or plain DNS upstream.

Getting DNS errors with DOH and plain DNS upstream as well.

"Webbplatsen kan inte nås Webbsidan på https://github.com/AdguardTeam/AdGuardHome/issues/new kan ligga nere för tillfället eller kan ha flyttats permanent till en ny webbadress.
ERR_NAME_RESOLUTION_FAILED"

ameshkov · 2019-01-02T20:42:39Z

@Vansinnet could you please attach a debug output? Run AG with -v

Vansinnet · 2019-01-02T20:57:58Z

@Vansinnet could you please attach a debug output? Run AG with -v

I will try my best here... I am complete garbage with Linux. Start AG like this?

sudo systemctl start adguard-home -v

There's no flag "-v" says terminal, so I must be doing it wrong. Also, what directory is the debug output generated to?

ameshkov · 2019-01-02T20:58:54Z

Nah, just run the binary directly:
./AdGuardHome -v

AG Home will print the verbose log to the output

Vansinnet · 2019-01-02T21:14:31Z

Nah, just run the binary directly:
./AdGuardHome -v

AG Home will print the verbose log to the output

Here's Cloudflare DOH failure

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: ; udp: 1452
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 192.168.1.96:57531
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 26139
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.wilderssecurity.com. IN A
proxy.(*Proxy).handleDNSRequest(): Upstream is https://cloudflare-dns.com:443/dns-query (0)
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 192.168.1.96:57531
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 26139
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.wilderssecurity.com. IN A
proxy.(*Proxy).handleDNSRequest(): Upstream is https://cloudflare-dns.com:443/dns-query (0)
proxy.(*Proxy).Resolve(): RTT: 324 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: SERVFAIL, id: 26139
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.wilderssecurity.com. IN A
proxy.(*Proxy).handleUDPPacket(): error handling DNS (udp) request: talking to dnsUpstream failed, cause: got an unexpected HTTP status code 400 from '104.16.111.25:443'
proxy.(*Proxy).Resolve(): RTT: 265 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 26139
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;www.wilderssecurity.com. IN A

;; ANSWER SECTION:
www.wilderssecurity.com. 300 IN CNAME wilderssecurity.com.
wilderssecurity.com. 300 IN A 45.33.17.126

;; ADDITIONAL SECTION:

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: ; udp: 1452
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 192.168.1.96:58306
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 46913
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.wilderssecurity.com. IN A
proxy.(*Proxy).handleDNSRequest(): Upstream is https://cloudflare-dns.com:443/dns-query (0)
proxy.(*Proxy).Resolve(): Serving cached response
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 46913
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.wilderssecurity.com. IN A

;; ANSWER SECTION:
www.wilderssecurity.com. 295 IN CNAME wilderssecurity.com.
wilderssecurity.com. 295 IN A 45.33.17.126
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 192.168.1.96:49675
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 11592
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;v10.events.data.microsoft.com. IN A
proxy.(*Proxy).handleDNSRequest(): Upstream is https://cloudflare-dns.com:443/dns-query (0)
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 192.168.1.96:49675
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 11592
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

ameshkov · 2019-01-02T21:21:09Z

@Vansinnet yeah that's another bug (with Cloudflare upstream): #520

prologic · 2019-01-03T12:41:27Z

I'm seeing this too with random SERVFAIL errors with host or dig. Does the work-around of using unencrypted regular DNS upstream servers like 8.8.8.8 work or that does also misbehave? -- I've had to go back to a CoreDNs deployment as this is annoyingly unreliable enough to be noticable and unproductive :/

uraimo · 2019-01-03T15:14:29Z

@prologic regular unencrypted DNS servers and encrypted DoH servers (other than cloudflare DoH, see #520, workaround dropping soon) work flawlessly as far as I can tell.

Vansinnet · 2019-01-03T17:16:40Z

@Vansinnet yeah that's another bug (with Cloudflare upstream): #520

Regular/plain 1.1.1.1 used (not DoT or DoH). How about these errors? It resulted in a DNS leak (showing both 1.1.1.1 and my ISP DNS)

### pi@raspberrypi:~ $ sudo /home/pi/AdGuardHome/AdGuardHome -v
2019/01/03 18:09:40 AdGuard Home web interface backend, version v0.92
2019/01/03 18:09:40 Current working directory is /home/pi/AdGuardHome
2019/01/03 18:09:40 main.upgradeConfig(): got schema version 2
2019/01/03 18:09:40 Reading YAML file: /home/pi/AdGuardHome/AdGuardHome.yaml
2019/01/03 18:09:40 Loading filter 1 contents to: /home/pi/AdGuardHome/data/filters/1.txt
2019/01/03 18:09:40 File /home/pi/AdGuardHome/data/filters/1.txt, id 1, length 502266
2019/01/03 18:09:40 Loading filter 3 contents to: /home/pi/AdGuardHome/data/filters/3.txt
2019/01/03 18:09:40 File /home/pi/AdGuardHome/data/filters/3.txt, id 3, length 1772528
2019/01/03 18:09:40 Writing YAML file: /home/pi/AdGuardHome/AdGuardHome.yaml
2019/01/03 18:09:40 Writing YAML file: /home/pi/AdGuardHome/AdGuardHome.yaml
2019/01/03 18:09:40 Creating dnsfilter
2019/01/03 18:09:41 Loading stats from querylog
2019/01/03 18:09:41 file "querylog.json": read 895 entries in 118.05979ms, 131.91µs/entry, 0 over 2h46m40s, 183.296288ms avg
2019/01/03 18:09:41 Starting the DNS proxy server
2019/01/03 18:09:41 Ratelimit is enabled and set to 20 rps
2019/01/03 18:09:41 The server is configured to refuse ANY requests
2019/01/03 18:09:41 DNS cache is enabled
2019/01/03 18:09:41 Creating the UDP server socket
2019/01/03 18:09:41 Listening to udp://[::]:53
2019/01/03 18:09:41 Go to http://192.168.1.32:3000
2019/01/03 18:09:41 Entering the UDP listener loop on [::]:53
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 192.168.1.1:17664
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 192.168.1.1:24738
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 8192
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;1_2pc02b9un1v5hjzp.dnsleak.privateinternetaccess.com.	IN	 A
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 1238
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;2_2pc02b9un1v5hjzp.dnsleak.privateinternetaccess.com.	IN	 A
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:53 (0)
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:53 (0)
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 192.168.1.1:40577
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 40067
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;3_2pc02b9un1v5hjzp.dnsleak.privateinternetaccess.com.	IN	 A
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:53 (0)
proxy.(*Proxy).handleUDPPacket(): Start handling new UDP packet from 192.168.1.1:33266
proxy.(*Proxy).logDNSMessage(): IN: ;; opcode: QUERY, status: NOERROR, id: 53470
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;sb.adtidy.org.	IN	 AAAA
proxy.(*Proxy).handleDNSRequest(): Upstream is 1.1.1.1:53 (0)
proxy.(*Proxy).Resolve(): RTT: 20 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: NOERROR, id: 53470
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;sb.adtidy.org.	IN	 AAAA

;; AUTHORITY SECTION:
adtidy.org.	2428	IN	SOA	kim.ns.cloudflare.com. dns.cloudflare.com. 2029750754 10000 2400 604800 3600
proxy.(*Proxy).Resolve(): RTT: 126 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: SERVFAIL, id: 8192
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;1_2pc02b9un1v5hjzp.dnsleak.privateinternetaccess.com.	IN	 A
proxy.(*Proxy).Resolve(): RTT: 109 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: SERVFAIL, id: 1238
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;2_2pc02b9un1v5hjzp.dnsleak.privateinternetaccess.com.	IN	 A
proxy.(*Proxy).Resolve(): RTT: 112 ms
proxy.(*Proxy).logDNSMessage(): OUT: ;; opcode: QUERY, status: SERVFAIL, id: 40067
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;3_2pc02b9un1v5hjzp.dnsleak.privateinternetaccess.com.	IN	 A
^C2019/01/03 18:10:01 Stopping the DNS proxy server
2019/01/03 18:10:01 udpListen.ReadFrom() returned because we're reading from a closed connection, exiting loop
2019/01/03 18:10:01 Stopped the DNS proxy server
2019/01/03 18:10:01 4 elements serialized via json in 1.391623ms: 1 kB, 341.75/entry, 347.905µs/entry
2019/01/03 18:10:01 check ok: 4 entries
2019/01/03 18:10:01 ok "querylog.json": 1367 bytes written

ameshkov · 2019-01-04T16:50:31Z

Reopening, this issue will be marked as fixed when we start using the newer dnsproxy version

Fix #520 #505 #518

ameshkov · 2019-01-04T18:28:20Z

Fixed by ddcfe7c

ibksturm · 2019-01-04T21:25:09Z

don‘t worry ^^ netflix crashed half of week and my wife couldn‘t watch „childout adventure of sabrina“ 👍👍👍

AGH doesn‘t have in version 0.92 an autoupdate, right? so i „have“ to wait... maybe till next week to update up to 0.92-fix1 🤩🤩🤩

prologic · 2019-01-04T23:18:27Z

Just build from source 😁

On Sat, 5 Jan 2019 at 07:25, Andreas Ziegler ***@***.***> wrote: don‘t worry ^^ netflix crashed half of week and my wife couldn‘t watch „childout adventure of sabrina“ 👍👍👍 AGH doesn‘t have in version 0.92 an autoupdate, right? so i „have“ to wait... maybe till next week to update up to 0.92-fix1 🤩🤩🤩 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#505 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABOv-m1A9C3ntLhS6p-lhzYpk8T48HKQks5u_8a3gaJpZM4ZlWVx> .

-- James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

ameshkov · 2019-01-04T23:26:14Z

@prologic I guess the idea is to help the wife to find a better show by not deploying any fixes :)

prologic · 2019-01-04T23:40:59Z

Lol my wife wants me to redeploy AGH so she can read articles on her news sites without all the crap noise that ads introduce on the page making it hard to read 🤣

On Sat, 5 Jan 2019 at 09:26, Andrey Meshkov ***@***.***> wrote: @prologic <https://github.com/prologic> I guess the idea is to help the wife to find a better show by not deploying any fixes :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#505 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABOv-vTb-OOcynvdWkB4QEcR-TpIjDnkks5u_-MYgaJpZM4ZlWVx> .

-- James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

ibksturm · 2019-01-05T00:10:38Z

@prologic i told my wife that i have build it from source (translatet in our native language)...
now she‘s thinking „sourcecode“ is a [fit in some german words] thing from star wars or star trek and netflix is still back

don‘t know if i should cry or lough....🤣👹

reading newssites without ads are a good opinion! wait... to do that i have to patch AGH and then she could watch again this .... on tv

not nice options lol 🤪

caio mentioned this issue Jan 2, 2019

DNS leaking #511

Closed

ameshkov added bug P2: High labels Jan 2, 2019

ameshkov mentioned this issue Jan 2, 2019

DNS-over-TLS upstream fails randomly AdguardTeam/dnsproxy#3

Closed

ameshkov added this to the v0.92-hotfix milestone Jan 2, 2019

ameshkov assigned hmage Jan 2, 2019

Vansinnet mentioned this issue Jan 3, 2019

Listening to TCP is mandatory in some cases #521

Closed

ameshkov closed this as completed in AdguardTeam/dnsproxy@1483e84 Jan 4, 2019

ameshkov reopened this Jan 4, 2019

hmage pushed a commit that referenced this issue Jan 4, 2019

Upgrade dnsproxy to 0.9.10

ddcfe7c

Fix #520 #505 #518

ameshkov closed this as completed Jan 4, 2019

brokoler mentioned this issue Feb 27, 2022

DNS leaks for every request to ISP DNS - Produced by Adguard Home v0.107.3 #4339

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

v0.92 - sporadic DNS error #505

v0.92 - sporadic DNS error #505

tomacco81 commented Dec 31, 2018

uraimo commented Dec 31, 2018 •

edited

Loading

ameshkov commented Dec 31, 2018

ameshkov commented Jan 2, 2019 •

edited

Loading

uraimo commented Jan 2, 2019

Vansinnet commented Jan 2, 2019

ameshkov commented Jan 2, 2019

Vansinnet commented Jan 2, 2019

ameshkov commented Jan 2, 2019

Vansinnet commented Jan 2, 2019

ameshkov commented Jan 2, 2019

prologic commented Jan 3, 2019

uraimo commented Jan 3, 2019

Vansinnet commented Jan 3, 2019 •

edited

Loading

ameshkov commented Jan 4, 2019

ameshkov commented Jan 4, 2019

ibksturm commented Jan 4, 2019

prologic commented Jan 4, 2019 via email

ameshkov commented Jan 4, 2019

prologic commented Jan 4, 2019 via email

ibksturm commented Jan 5, 2019

v0.92 - sporadic DNS error #505

v0.92 - sporadic DNS error #505

Comments

tomacco81 commented Dec 31, 2018

Steps to reproduce

Expected behavior

Actual behavior

Your environment

uraimo commented Dec 31, 2018 • edited Loading

ameshkov commented Dec 31, 2018

ameshkov commented Jan 2, 2019 • edited Loading

uraimo commented Jan 2, 2019

Vansinnet commented Jan 2, 2019

ameshkov commented Jan 2, 2019

Vansinnet commented Jan 2, 2019

ameshkov commented Jan 2, 2019

Vansinnet commented Jan 2, 2019

ameshkov commented Jan 2, 2019

prologic commented Jan 3, 2019

uraimo commented Jan 3, 2019

Vansinnet commented Jan 3, 2019 • edited Loading

ameshkov commented Jan 4, 2019

ameshkov commented Jan 4, 2019

ibksturm commented Jan 4, 2019

prologic commented Jan 4, 2019 via email

ameshkov commented Jan 4, 2019

prologic commented Jan 4, 2019 via email

ibksturm commented Jan 5, 2019

uraimo commented Dec 31, 2018 •

edited

Loading

ameshkov commented Jan 2, 2019 •

edited

Loading

Vansinnet commented Jan 3, 2019 •

edited

Loading