0

New routing issue with 45.90.28.0

NextDNS Diag 20201215.txt

As of about 30 minutes ago (8pm EST) I lost ability to contact 45.90.28.0.   45.90.30.0 routes to a server in Brazil (I'm in Eastern USA), this has been happening for a few months and was reported previously. I'm working around it by hardcoding the anexia-mnz-1 IP address on my laptop but for iOS devices that use a profile/app, I'm out of luck. 

I attempted to send a new report from the diag tool at 8:33 pm but received an error:
Post unsuccessful: status 400, {"error":"0: instance requires property \"Primary\"\n"}

Contents of the diag output are attached if that's of help (replaced my IP with the subnet for some semblance of privacy). Any suggestions on how to get a connection to a North American server via the 45.90.x.x IPs?

5 replies

null
    • olivier
    • 3 yrs ago
    • Reported - view

    Can you please try agin?

      • Chris_Leidich
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey Sure... Unfortunately, still having the issue. 28.0 dies at hop 14, looks like might be Hong Kong? 30.0 is still up, but still routing to South America. Appreciate your help in looking into this!
       

      Tracing route to 45.90.28.0 over a maximum of 30 hops

        1     2 ms     2 ms     3 ms  192.168.86.1
        2     *        *        *     Request timed out.
        3    16 ms    14 ms    16 ms  207.44.124.97
        4    12 ms    11 ms    12 ms  207.44.120.13
        5    14 ms    15 ms    15 ms  207.44.126.97
        6    26 ms    21 ms    20 ms  172.16.10.29
        7    21 ms    20 ms    20 ms  206.126.237.40
        8    19 ms    20 ms    20 ms  85.202.80.3
        9     *        *        *     Request timed out.
       10     *        *        *     Request timed out.
       11     *        *        *     Request timed out.
       12     *        *        *     Request timed out.
       13     *        *        *     Request timed out.
       14   264 ms   263 ms   264 ms  182.255.35.1
       15     *        *        *     Request timed out.
       16     *        *        *     Request timed out.
       17     *        *        *     Request timed out.

      Tracing route to 45.90.30.0 over a maximum of 30 hops

        1     2 ms     2 ms     2 ms  192.168.86.1
        2     *        *        *     Request timed out.
        3    12 ms    11 ms    11 ms  207.44.124.97
        4    12 ms    11 ms    11 ms  207.44.120.13
        5    14 ms    14 ms    14 ms  207.44.126.97
        6    20 ms    20 ms    21 ms  172.16.10.31
        7    45 ms    45 ms     *     206.126.236.205
        8   162 ms   150 ms   150 ms  168.197.23.186
        9     *      155 ms   155 ms  168.197.21.142
       10     *        *        *     Request timed out.
       11   157 ms   174 ms     *     201.49.108.17
       12   156 ms   159 ms   159 ms  45.90.30.0

    • Angus_Lee
    • 3 yrs ago
    • Reported - view

    I'm from Hong Kong and have the same issue too

    the ping.nextdns.io result:

      anexia-hkg         3 ms

      gsl-sin           35 ms

      rix-sin           36 ms

      anexia-sin        38 ms

    ■ vultr-sin         39 ms  (secondary)

      zepto-sel         48 ms

      vultr-tyo         52 ms

      rix-tyo           53 ms

      gc-bom            97 ms

      ls-pnq           102 ms

    ■ dns1.nextdns.io error (primary)

    NextDNS diag.txt
    • Chris_Gilbert
    • 3 yrs ago
    • Reported - view

    I am in the UK. I use dnscrypt-proxy and get no dns resolving this morning. I cannot ping 45.90.28.0 or 
    45.90.28.52 so I suspect the routing is wrong.  It works from the Netherlands, Germany and the US.

    Could we have the setup details for a backup resolver in dnscrypt please - at the moment if the primary fails for whatever reason we lose all connectivity?

      • Chris_Gilbert
      • 3 yrs ago
      • Reported - view

      Chris Gilbert   resolver: 141.101.70.43
      Traceroute for primary IPv4 (45.90.28.0)
          1    192.168.1.1    3ms   2ms   2ms
          2    78.144.1.17    6ms   6ms   5ms
          3    78.144.1.16   14ms  15ms  12ms
          4 195.66.226.180    8ms   8ms   8ms
          5  5.254.112.198   13ms  13ms  13ms
          6    5.254.73.90   20ms  20ms  20ms
          7     5.254.11.6   19ms  20ms  19ms
          8  5.254.104.102   24ms  23ms  23ms
          9                   *     *     *
         10                   *     *     *
         11                   *     *     *
         12                   *     *     *
         13                   *     *     *
         14                   *     *     *
         15                   *     *     *
         16                   *     *     *
         17                   *     *     *
         18                   *     *     *
         19                   *     *     *
         20                   *     *     *
      Traceroute for secondary IPv4 (45.90.30.0)
          1    192.168.1.1    2ms   3ms   2ms
          2    78.144.1.17   15ms  12ms   5ms
          3    78.144.1.16   12ms  11ms  17ms
          4 195.66.226.113   13ms  12ms  14ms
          5     45.90.30.0    8ms   8ms  10ms
      Fetching PoP name for primary IPv4 (45.90.28.0)
      Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.28.0:443: connect: operation timed out
      Fetching PoP name for secondary IPv4 (45.90.30.0)
        anexia-lon: 8.132ms
      Pinging PoPs
        anexia-lon: 899µs
        zepto-lon: 896.6µs
        vultr-lon: 904.5µs
        zepto-bru: 1.4262ms
        vultr-ams: 1.4935ms
        virtua-par: 1.6ms
        anexia-par: 1.7207ms
        netbarista-par: 1.9ms
        anexia-ams: 3.0757ms
        zepto-dub: 3.0465ms
      Do you want to send this report? [Y/n]: y
      Optional email in case we need additional info: chris@gilbertcloud.com
      Post unsuccessful: status 400
      {"error":"0: instance requires property \"Primary\"\n"}%

Login to reply

Content aside

  • 2 yrs agoLast active
  • 5Replies
  • 524Views
  • 5 Following