3

Service down?

Is there a problem with the service?

40 replies

null
    • Hans_Geiblinger
    • 4 yrs ago
    • Reported - view

    I've been running into the same issues lately as well, not sure going crazy or what? Same exact thing..... You'll be asked to run the collection tool when it happens to upload a diag. Maybe you can make more progress? What kind of setup are you using?

     

    Here's my thread: https://help.nextdns.io/t/60hzvs5/anycast-dns1-nextdns-io-error-anycast1

    • iOS Developer
    • Rob
    • 4 yrs ago
    • Reported - view

    I’m suddenly getting this on my iOS devices: 

    This network is blocking encrypted DNS traffic.

The names of websites and other servers your devices accesses on this network may be monitored and recorded by other devices on this network.

    If I disable NextDNS the warning disappears and DNS does work...

    • iOS Developer
    • Rob
    • 4 yrs ago
    • Reported - view

    As paying customers we could use (semi) real-time support now!

    Do we really need to wait until a NextDNS employee checks this forum?

    (not good enough if the service is really down right now)

    • Chris_Leidich
    • 4 yrs ago
    • Reported - view

    I noticed that Ultralow was on the fritz earlier, the CLI also failed over to Dallas (normally IAD or XPS). Seems to be running better now, but not sure what was happening.

    • olivier
    • 4 yrs ago
    • Official response
    • Reported - view

    We had a bad push that affected ultralow steering in some regions. This has been rolled back a few minutes later. Sorry for the inconvenience.

      • iamtheanon
      • 4 yrs ago
      • Reported - view

      Olivier Poitrey I am currently still getting the following: 

        vultr-mia                 error
  anexia-mia                error
  atlantic-orl              error
  premiumrdp-jax            error
  smarthost-jax             error
  vultr-atl                 error
  anexia-atl                error
  tier-clt                  error
  hydron-clt                error
  anexia-mnz                error
  anycast.dns1.nextdns.io   error  (anycast1)
  anycast.dns2.nextdns.io   error  (anycast2)
  dns1.nextdns.io           error  (ultralow1)
  dns2.nextdns.io           error  (ultralow2)

      I use DoH using the secure DNS feature on my browser only at this moment. While I am am able to browse the latency has increased a lot since the past few hours. 

      • olivier
      • 4 yrs ago
      • Reported - view

      Gaurav which browser is that? What version?

      • iamtheanon
      • 4 yrs ago
      • Reported - view

      Olivier Poitrey Using Brave Browser, the latest stable version. 

      • olivier
      • 4 yrs ago
      • Reported - view

      Gaurav with DoH setup in Brave?

      • iamtheanon
      • 4 yrs ago
      • Reported - view

      Olivier Poitrey Yes, the secure DNS setting in the browser itself with my configuration. Right now, however, it's resolving properly. 

      • olivier
      • 4 yrs ago
      • Reported - view

      Gaurav this is due to our rollout of HTTP/3. It created some problems with chrome based browsers. We disabled it for now. Do you have IPv6?

      • iamtheanon
      • 4 yrs ago
      • Reported - view

      Olivier Poitrey Oh. Hopefully the next time you try out the HTTP/3 release you are better prepared and successful. 

      As for ipv6 my ISP currently doesn't support it fully yet. Though, they plan to next month onwards. 

    • Michiel
    • 4 yrs ago
    • Reported - view

    Thanks!

    • mint_engine
    • 4 yrs ago
    • Reported - view

    Looks like the problem is back again. DOH is down for me. IP works fine.

      • olivier
      • 4 yrs ago
      • Reported - view

      gc what do you get for "nslookup dns.nextdns.io" and "https://test.nextdns.io"

    • mint_engine
    • 4 yrs ago
    • Reported - view
    nslookup dns.nextdns.io
Server:         192.168.2.3
Address:        192.168.2.3#53
** server can't find dns.nextdns.io: SERVFAIL

nslookup https://test.nextdns.io
Server:         192.168.2.3
Address:        192.168.2.3#53
** server can't find https://test.nextdns.io: SERVFAIL

     

    if i disable dnssec 

    nslookup dns.nextdns.io
Server:         192.168.2.3
Address:        192.168.2.3#53
Non-authoritative answer:
dns.nextdns.io  canonical name = steering.nextdns.io.
Name:   steering.nextdns.io
Address: 188.172.221.9
Name:   steering.nextdns.io
Address: 155.138.130.135
Name:   steering.nextdns.io
Address: 2001:19f0:5:663d:5400:2ff:fece:2f14
Name:   steering.nextdns.io
Address: 2a00:11c0:46:4::5

nslookup https://test.nextdns.io
Server:         192.168.2.3
Address:        192.168.2.3#53
** server can't find https://test.nextdns.io: SERVFAIL
    • Qadhi
    • 4 yrs ago
    • Reported - view

    an hour ago my nextdns service went down too which is still not working.

    • olivier
    • 4 yrs ago
    • Reported - view

    A fix is being deployed.

      • thor
      • 4 yrs ago
      • Reported - view

      thor Olivier Poitrey or your linux client on raspberry and other distros does need an update but for that your mirror should be accessible.

    • thor
    • 4 yrs ago
    • Reported - view

    It is still happening. You have still, at least on CH, downtime every minutes or every x queries.

    Plus your mirror for linux installation of your client is unreachable. It is happening on every devices I have so it's still the case i guess for the other customers too. 

      • olivier
      • 4 yrs ago
      • Reported - view

      thor please show the error.

      • thor
      • 4 yrs ago
      • Reported - view

      Olivier Poitrey which one ? Sorry to ask but you could see for yourself first

      if you are talking about your mirror: 

       Ign :1 https://dl.bintray.com/nextdns/deb stable InRelease 

           this is because of I had errors earlier today and for several days now so => mirror down

      where is the log for your client in house? or do I need to activate a setting for that ? 

      I have plenty of  

      ERR_NAME_NOT_RESOLVED

      and my dns server are pihole and no my setup is working perfectly

      the raspberries pi having this setup has 2 subresolvers for pihole which is nextdns and unbound and every x queries because I have a lot of BOGUS in direction to your dns resolver client so....

      • olivier
      • 4 yrs ago
      • Reported - view

      thor I can’t reproduce the bintray issue. Are you sure it is not blocked? What do you get for “dig dl.bintray.com”.

      You setup sound very complex. Can you reproduce the issue with a simpler setup directly on your host for instance (or cli alone on your rpi).

      • thor
      • 4 yrs ago
      • Reported - view

      Olivier Poitrey hardly doubtful  

      ; <<>> DiG 9.11.5-P4-5.1+deb10u3-Raspbian <<>> dl.bintray.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50703
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1472
;; QUESTION SECTION:
;dl.bintray.com.                        IN      A
;; ANSWER SECTION:
dl.bintray.com.         3600    IN      A       3.121.249.232
dl.bintray.com.         3600    IN      A       52.29.138.222

so not a  dns problem apparently... so yeah a problem for the mirror itself
      • thor
      • 4 yrs ago
      • Reported - view

      Olivier Poitrey it's not complex at all.

      pihole is the resolver for my LAN and filter at the same time. Pihole is asking for dnsresolver wether it's official ones like quad9 or personal one.

      unbound take much more time in general unless it's in cache so the forwarder(as you pretty well know because of the mechanics of dns) which is chosen is yours since it's normally under less than 40 ms.  

      So its not complex at all and sorry but for this case I pretty much have much confidence in a implementation like pihole than yours than doesn't offer a log system internally and since you are not telling me : put that in your config nextdns.conf I guess there is no log option.... 

      The only thing that should be done to be sure it's to analyze your technical logs of your server to see how much request doesn't end up as resolved... But I can't do that for you 

Login to reply

Content aside

  • 3 Likes
  • 4 yrs agoLast active
  • 40Replies
  • 812Views
  • 11 Following