1

DNS have high ping issue also routed via wrong PoP

Hello NextDNS team,

I have these ip addresses 45.90.28.60, 45.90.30.60 in my profile by default and only I can use them on the router to use blocking rules, can these ip addresses be changed to those closer to me (217.146.2.63, 45.150.243.134) and have a faster response than the current ones ?

Thanks in advance.

https://nextdns.io/diag/e9af0b80-6c19-11ef-a2cb-a1eac20365ff

 

 

3 replies

null
    • Ross.1
    • 2 mths ago
    • Reported - view

    kind reminder

    • Gunter_Grodotzki
    • 2 mths ago
    • Reported - view

    I see the same issue from Stockholm/Bahnhof (one of the largest ISP):

    $ mtr --report-wide 45.90.28.80
    Start: 2024-09-13T13:04:02+0000
    HOST: box.office-sth.digitaltolk.net          Loss%   Snt   Last   Avg  Best  Wrst StDev
      1.|-- 192.168.50.1                             0.0%    10    0.2   0.2   0.1   0.3   0.1
      2.|-- h-178-174-168-17.NA.cust.bahnhof.se      0.0%    10    1.6  35.8   1.6  79.5  27.2
      3.|-- sto-bsg15-ar1.sto-soder-dr2.bahnhof.net  0.0%    10    5.6   5.8   0.8  39.9  12.1
      4.|-- 176.10.181.58                            0.0%    10    1.0   1.9   0.9   8.8   2.4
      5.|-- sto-sand-dr1.sto-kn6-dr1.bahnhof.net     0.0%    10    1.1   3.2   0.9  22.4   6.7
      6.|-- sto-kn5-dr2.sto-kn5-dr1.bahnhof.net      0.0%    10    2.9   2.0   0.9   6.6   1.7
      7.|-- sto-kn5-dr1.sto-kn4-dr1.bahnhof.net      0.0%    10   46.0  40.6  11.7  66.7  19.8
      8.|-- sto-kn4-dr1.sto-cr1.bahnhof.net          0.0%    10    1.4   1.4   1.2   1.6   0.1
      9.|-- dns1.nextdns.io                          0.0%    10   23.0  23.0  22.9  23.1   0.1

     

    Same provider, different location:

    $ mtr --report-wide 45.90.28.80
    Start: 2024-09-13T13:07:04+0000
    HOST: lab.swag.grodotzki.com                    Loss%   Snt   Last   Avg  Best  Wrst StDev
      1.|-- 192.168.42.1                               0.0%    10    0.4   0.4   0.4   0.5   0.1
      2.|-- gw487.A498.priv.bahnhof.se                 0.0%    10    1.8   2.1   1.0   8.5   2.3
      3.|-- sto-orbykc03-ar1.sto-orby-dr1.bahnhof.net  0.0%    10    1.4   3.3   1.2  19.8   5.8
      4.|-- sto-orby-dr1.sto-ars-dr1.bahnhof.net       0.0%    10    1.5   6.8   1.2  54.0  16.6
      5.|-- sto-ars-dr1.sto-ens-dr1.bahnhof.net        0.0%    10    5.0  19.1   1.6  53.8  15.9
      6.|-- sto-ens-dr1.sto-ss-dr1.bahnhof.net         0.0%    10    8.0   7.8   1.8  19.5   6.2
      7.|-- sto-ss-dr1.sto-sh-dr1.bahnhof.net          0.0%    10    2.1   2.0   1.8   2.3   0.2
      8.|-- sto-sh-dr1.sto-kn5-dr2.bahnhof.net         0.0%    10    3.0   1.9   1.4   3.0   0.6
      9.|-- sto-kn5-dr2.sto-kn5-dr1.bahnhof.net        0.0%    10    1.6   1.6   1.3   2.6   0.4
     10.|-- sto-kn5-dr1.sto-kn4-dr1.bahnhof.net        0.0%    10    2.1   2.5   1.3   8.2   2.1
     11.|-- sto-kn4-dr1.sto-cr1.bahnhof.net            0.0%    10    1.8   1.8   1.5   2.2   0.2
     12.|-- dns1.nextdns.io                            0.0%    10   23.5  23.3  23.3  23.5   0.1
    • NextDNs
    • 2 mths ago
    • Reported - view

    It wouldn’t work with linked IP. Ultralow only works with encrypted protocols like DoH or DoT

Content aside

  • 1 Likes
  • 2 mths agoLast active
  • 3Replies
  • 105Views
  • 4 Following