0

Network Latency Issues - Philippines

Hi NextDNS,

New annual subscriber here, I am being assigned to a different DNS with high latency on my OpenWRT setup.

https://nextdns.io/diag/6c68c1a0-4e69-11ec-b0d6-917729b7e32b

Please see above for your reference.

11 replies

null
    • MarkG
    • 2 yrs ago
    • Reported - view

    Try these:

    https://ultralow.dns1.nextdns.io/clientid
    https://ultralow.dns2.nextdns.io/clientid

    Better yet use Adguard Home UI to run NextDNS:

    https://forum.openwrt.org/t/howto-running-adguard-home-on-openwrt/51678

      • Hey
      • 2 yrs ago
      • Reported - view

      MarkG That defeats the whole purpose of having a cloud based DNS, if you're going to have to maintain and fix everything yourself and make sure everything is up to date. I mean, at that point you have to make a VPN or a tunnel to connect outside of your home or go through a ton of loops to make function like NextDNS. I think the NextDNS support team finding the problem and fixing it would be a better option. 

      • nikohd
      • 2 yrs ago
      • Reported - view

      MarkG I appreciate the reply. I’m going to try this out and report back. Initially was expecting a reply since I got a feedback to submit a network diag. No worries tho. 

      • nikohd
      • 2 yrs ago
      • Reported - view

      MarkG 

      Just an update. I have installed AdGuard Home on my OpenWRT Router. It is working well now. Big thanks!

      I have a few questions tho.

      1. What Bootstrap DNS' should I use? I am currently using the following:

      1.1.1.1
      1.0.0.1
      2606:4700:4700::1111
      2606:4700:4700::1001
      8.8.8.8
      8.8.4.4
      2001:4860:4860::8888
      2001:4860:4860::8844

      2. How do I forward the Device Info to NextDNS from AdGuard Home?

      Do I just enable "Enable EDNS client subnet"?

      • losnad
      • 2 yrs ago
      • Reported - view

      1. NextDNS ip's are

      45.90.28.0

      45.90.30.0

      2a07:a8c0::

      2a07:a8c1::

      2. my.nextdns.io - Setup - Identify your devices

      Read https://help.nextdns.io/t/m1hmv04/what-is-edns-client-subnet-ecs

      • nikohd
      • 2 yrs ago
      • Reported - view

      losnad Appreciate it! Thank you

      • nikohd
      • 2 yrs ago
      • Reported - view

      losnad Can anyone help me with big average of 1000ms processing time.

      I'm using the default NextDNS filters + AdGuard.

       

      I'm guessing because these are blocked.

       

      play.google.com

      Type: A, Plain DNS

      Processed

      2610 ms

      127.0.0.1

      localhost

       

      signaler-pa.clients6.google.com

      Type: A, Plain DNS

      Processed

      675 ms

      127.0.0.1

      localhost

       

      signaler-pa.clients6.google.com

      Type: AAAA, Plain DNS

      Processed

      2602 ms

      127.0.0.1

      localhost

       

      signaler-pa.clients6.google.com

      Type: A, Plain DNS

      Processed

      2593 ms

      127.0.0.1

      localhost

       

      signaler-pa.clients6.google.com

      Type: AAAA, Plain DNS

      Processed

      656 ms

      127.0.0.1

      localhost

       

      updates2.signal.org

      Type: AAAA, Plain DNS

      Processed

      29 ms

      127.0.0.1

      localhost

       

      updates2.signal.org

      Type: A, Plain DNS

      Processed

      28 ms

      127.0.0.1

      localhost

       

      discord.com

      Type: AAAA, Plain DNS

      Processed

      28 ms

      127.0.0.1

      localhost

       

      discord.com

      Type: A, Plain DNS

      Processed

      27 ms

      127.0.0.1

      localhost

       

      c.msn.com

      Type: AAAA, Plain DNS

      Processed

      794 ms

      127.0.0.1

      localhost

       

      c.msn.com

      Type: A, Plain DNS

      Processed

      784 ms

      127.0.0.1

      localhost

       

      sb.scorecardresearch.com

      Type: AAAA, Plain DNS

      Processed

      784 ms

      127.0.0.1

      localhost

      • nikohd
      • 2 yrs ago
      • Reported - view

      Niko Jaro 

      EDIT: I was able to lower the average processing time to 30ms by doing the following:

      1. Use NextDNS IPv6 addresses over DoH and DoT

      2. Use Google DNS as the Bootstrap DNS

      3. Using the "Load-Balancing" algorithm over the recommended Parallel

      Do NextDNS block parallel DNS requests?

      • frsfrt
      • 2 yrs ago
      • Reported - view

      Niko Jaro if you use Google as a boostrap DNS, it doesn't work with Next DNS  , since every time NextDNS blocked something, Google DNS will solve it

      • MarkG
      • 2 yrs ago
      • Reported - view

      frsfrt What would be a could alternative then?

    • MarkG
    • 2 yrs ago
    • Reported - view

    At this point in time you have to improvise especially if you're not getting any response from NextDNS Team

Login to reply

Content aside

  • 2 yrs agoLast active
  • 11Replies
  • 347Views
  • 4 Following