dnsproxy
dnsproxy copied to clipboard
AdguardTeam
[Enhancement] DNS Queries in Errout?!
DNS queries appears in errout and only when verbose mode is enabled. I'm using DNSProxy on SecureDnsClient and I wanted to show DNS queries on log window, filtering out only queries among all that data is a heavy job on cpu. It would be great if you could write queries on stdout and without verbose mode. Thank you.
Is this implemented in the 'master' now with this PR? https://github.com/AdguardTeam/dnsproxy/commit/d1469a436f425b28be0e0d3d164cd54b9d6b6d22
Today I see lots of failed queries in the system-log (stdout) that has not been shown before.
Aug 22 08:00:08 admin: 2023/08/22 06:00:08 [error] upstream quic://<redacted>.dns.nextdns.io:853 failed to exchange ;home-devices.googleapis.com. IN A in 1m43.61346775s. Cause: opening quic connection to quic://<redacted>.dns.nextdns.io:853: timeout: no recent network activity
Aug 22 08:00:13 admin: 2023/08/22 06:00:13 [error] upstream quic://<redacted>.dns.nextdns.io:853 failed to exchange ;apps.mzstatic.com. IN HTTPS in 1m48.1260153s. Cause: opening quic connection to quic://<redacted>.dns.nextdns.io:853: timeout: no recent network activity
Aug 22 08:00:13 admin: 2023/08/22 06:00:13 [error] upstream quic://<redacted>.dns.nextdns.io:853 failed to exchange ;mtalk.google.com. IN A in 1m47.883761501s. Cause: opening quic connection to quic://<redacted>.dns.nextdns.io:853: timeout: no recent network activity
Aug 22 08:00:13 admin: 2023/08/22 06:00:13 [error] upstream quic://<redacted>.dns.nextdns.io:853 failed to exchange ;gateway.icloud.com. IN A in 1m48.126283981s. Cause: opening quic connection to quic://<redacted>.dns.nextdns.io:853: timeout: no recent network activity
Aug 22 08:02:57 admin: 2023/08/22 06:02:57 [error] upstream tls://<redacted>.dns.nextdns.io:853 failed to exchange ;home-devices.googleapis.com. IN A in 3.059977312s. Cause: getting conn to tls://<redacted>.dns.nextdns.io:853: connecting to <redacted>.dns.nextdns.io: all dialers failed: dial tcp 192.36.27.86:853: connect: connection timed out
Aug 22 08:02:57 admin: 2023/08/22 06:02:57 [error] upstream tls://<redacted>.dns.nextdns.io:853 failed to exchange ;ccp-lh.googleusercontent.com. IN A in 3.071914337s. Cause: getting conn to tls://<redacted>.dns.nextdns.io:853: connecting to <redacted>.dns.nextdns.io: all dialers failed: dial tcp 192.36.27.86:853: connect: connection timed out
Aug 22 08:02:57 admin: 2023/08/22 06:02:57 [error] upstream tls://<redacted>.dns.nextdns.io:853 failed to exchange ;home-devices.googleapis.com. IN A in 3.070764225s. Cause: getting conn to tls://<redacted>.dns.nextdns.io:853: connecting to <redacted>.dns.nextdns.io: all dialers failed: dial tcp 192.36.27.86:853: connect: connection timed out
Aug 22 08:02:57 admin: 2023/08/22 06:02:57 [error] upstream tls://<redacted>.dns.nextdns.io:853 failed to exchange ;mtalk.google.com. IN A in 3.060166194s. Cause: getting conn to tls://<redacted>.dns.nextdns.io:853: connecting to <redacted>.dns.nextdns.io: all dialers failed: dial tcp 192.36.27.86:853: connect: connection timed out
