0

Issues with NextDNS with DNSCrypt ( Am I doing something wrong)?

sudo: unable to resolve host DNSCrypt: Temporary failure in name resolution
● dnscrypt-proxy.service - Encrypted/authenticated DNS proxy
   Loaded: loaded (/etc/systemd/system/dnscrypt-proxy.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2021-02-17 17:16:04 EST; 1h 52min ago
 Main PID: 356 (dnscrypt-proxy)
    Tasks: 9 (limit: 4915)
   CGroup: /system.slice/dnscrypt-proxy.service
           └─356 /opt/dnscrypt-proxy/dnscrypt-proxy -config dnscrypt-proxy.toml

Feb 17 17:16:14 DNSCrypt dnscrypt-proxy[356]: [2021-02-17 17:16:14] [NOTICE] Now listening to 127.0.0.1:5054 [TCP]
Feb 17 17:16:14 DNSCrypt dnscrypt-proxy[356]: [2021-02-17 17:16:14] [NOTICE] Now listening to [::1]:5054 [UDP]
Feb 17 17:16:14 DNSCrypt dnscrypt-proxy[356]: [2021-02-17 17:16:14] [NOTICE] Now listening to [::1]:5054 [TCP]
Feb 17 17:16:14 DNSCrypt dnscrypt-proxy[356]: [2021-02-17 17:16:14] [NOTICE] Source [public-resolvers] loaded
Feb 17 17:16:14 DNSCrypt dnscrypt-proxy[356]: [2021-02-17 17:16:14] [NOTICE] Source [relays] loaded
Feb 17 17:16:14 DNSCrypt dnscrypt-proxy[356]: [2021-02-17 17:16:14] [NOTICE] Firefox workaround initialized
Feb 17 17:16:20 DNSCrypt dnscrypt-proxy[356]: [2021-02-17 17:16:20] [ERROR] Get "https://dns.nextdns.io/23aa23?dns=yv4BAAABAAAAAAABAAACAAEAACkQAAAAAAAAFAAMABD94dA8iAq2I_Yp22bgkRkt": dial tcp 45.90.28.0:443: connect: no route to host
Feb 17 17:16:20 DNSCrypt dnscrypt-proxy[356]: [2021-02-17 17:16:20] [NOTICE] dnscrypt-proxy is waiting for at least one server to be reachable
Feb 17 17:16:51 DNSCrypt dnscrypt-proxy[356]: [2021-02-17 17:16:51] [NOTICE] [NextDNS-23aa23] OK (DoH) - rtt: 26ms
Feb 17 17:16:51 DNSCrypt dnscrypt-proxy[356]: [2021-02-17 17:16:51] [NOTICE] Server with the lowest initial latency: NextDNS-23aa23 (rtt: 26ms)

3 replies

null
    • olivier
    • 3 yrs ago
    • Reported - view

    Please describe the issue you are having. The logs seems to say you are connected correctly.

      • jade_light
      • 3 yrs ago
      • Reported - view

      Olivier , I'm wondering the line [ERROR] Get "https://dns.nextdns.io/23aa23?dns=yv4BAAABAAAAAAABAAACAAEAACkQAAAAAAAAFAAMABD94dA8iAq2I_Yp22bgkRkt": dial tcp 45.90.28.0:443: connect: no route to host

       

      I checked this morning and noticed  (rtt: 4798ms) and [ERROR] Get "https://dns.nextdns.io/23aa23?dns=yv4BAAABAAAAAAABAAACAAEAACkQAAAAAAAAFAAMABB7nb12RrOk2izMeg-JgVly": context deadline exceeded (Client.Timeout exceede

      Blew is the full summary

       

      Main PID: 370 (dnscrypt-proxy)
          Tasks: 10 (limit: 4915)
         CGroup: /system.slice/dnscrypt-proxy.service
                 └─370 /opt/dnscrypt-proxy/dnscrypt-proxy -config dnscrypt-proxy.toml

      Feb 18 12:57:02 DNSCryptServer dnscrypt-proxy[370]: [2021-02-18 12:57:02] [NOTICE] Network connectivity detected
      Feb 18 12:57:02 DNSCryptServer dnscrypt-proxy[370]: [2021-02-18 12:57:02] [NOTICE] Now listening to 127.0.0.1:5054 [UDP]
      Feb 18 12:57:02 DNSCryptServer dnscrypt-proxy[370]: [2021-02-18 12:57:02] [NOTICE] Now listening to 127.0.0.1:5054 [TCP]
      Feb 18 12:57:02 DNSCryptServer dnscrypt-proxy[370]: [2021-02-18 12:57:02] [NOTICE] Now listening to [::1]:5054 [UDP]
      Feb 18 12:57:02 DNSCryptServer dnscrypt-proxy[370]: [2021-02-18 12:57:02] [NOTICE] Now listening to [::1]:5054 [TCP]
      Feb 18 12:57:02 DNSCryptServer dnscrypt-proxy[370]: [2021-02-18 12:57:02] [NOTICE] Firefox workaround initialized
      Feb 18 12:57:15 DNSCryptServer dnscrypt-proxy[370]: [2021-02-18 12:57:15] [ERROR] Get "https://dns.nextdns.io/23aa23?dns=yv4BAAABAAAAAAABAAACAAEAACkQAAAAAAAAFAAMABB7nb12RrOk2izMeg-JgVly": context deadline exceeded (Client.Timeout exceede
      Feb 18 12:57:15 DNSCryptServer dnscrypt-proxy[370]: [2021-02-18 12:57:15] [NOTICE] dnscrypt-proxy is waiting for at least one server to be reachable
      Feb 18 12:57:34 DNSCryptServer dnscrypt-proxy[370]: [2021-02-18 12:57:34] [NOTICE] [NextDNS-23aa23] OK (DoH) - rtt: 4798ms
      Feb 18 12:57:34 DNSCryptServer dnscrypt-proxy[370]: [2021-02-18 12:57:34] [NOTICE] Server with the lowest initial latency: NextDNS-23aa23 (rtt: 4798ms)

      • olivier
      • 3 yrs ago
      • Reported - view

      RK do you have the same issue with the CLI (https://nextdns.io/cli)?

Login to reply

Content aside

  • 3 yrs agoLast active
  • 3Replies
  • 754Views
  • 2 Following