0

IP possibly blocklisted?

I accidentally ran an access-log analyzer script on a NextDNS-enabled computer yesterday that would have sent a few hundred thousand requests from my "linked IP" to the (generic) NextDNS servers 45.90.28.234 and 45.90.30.234. (I discovered the error when my other computers started to fail to resolve every hostname.) I replaced the NextDNS servers in my router and things started to work again, but if I try to go back to NextDNS name resolution continues to fail. I suspect my IP address has been added to a blocklist; is there a way to get off of it? I've updated the code that sent the requests to behave more rationally and distribute DNS requests to a number of different providers, so it shouldn't happen again.

In case it's of use, here's a report from ping.nextdns.io. Unfortunately I can't provide a diag report while on NextDNS because I can't look up the NextDNS server names.

vultr-chi                 61 ms
  edis-ymq                  61 ms
  zepto-ymq                 62 ms
  teraswitch-pit            70 ms
  anexia-chi                73 ms
  incx-dtw                 100 ms
  zepto-iad                144 ms
  router-pit               231 ms
  anexia-yto                error
  vultr-yto                 error
  anycast.dns1.nextdns.io   error  (anycast1)
  anycast.dns2.nextdns.io   error  (anycast2)
  dns1.nextdns.io           error  (ultralow1)
  dns2.nextdns.io           error  (ultralow2)

Thanks for any help you can provide.

2 replies

null
    • Peter_J
    • 6 mths ago
    • Reported - view

    I managed to get the diag report to work by hardcoding the IP for nextdns.io in my /etc/hosts file, but it failed to post, so here's the text:

    Resolvers:  192.168.2.1
    Testing IPv6 connectivity
      available: false
    Fetching https://test.nextdns.io
      Fetch error: Get "https://test.nextdns.io": dial tcp 188.172.221.9:443: i/o timeout
    Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
      edis-ymq: 26.341ms
    Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
      zepto-ymq: 27.721ms
    Fetching PoP name for anycast 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 anycast secondary IPv4 (45.90.30.0)
    Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.30.0:443: connect: operation timed out
    Pinging PoPs
      vultr-chi: 23.84ms
      zepto-ymq: 30.138ms
      edis-ymq: 28.992ms
      anexia-chi: 35.91ms
      teraswitch-pit: 35.592ms
      incx-dtw: 41.858ms
      zepto-iad: 41.933ms
      router-pit: 79.873ms
    Traceroute for ultra low latency primary IPv4 (92.243.64.136)
        1    192.168.2.1    1ms   0ms   0ms
        2   198.2.98.193   13ms  15ms  14ms
        3  104.153.24.70   14ms  13ms  13ms
        4  104.153.24.69   17ms  22ms  20ms
        5 64.140.112.173   16ms  15ms  21ms
        6 64.140.112.172   23ms  24ms  23ms
        7 64.140.112.176   23ms  18ms  18ms
        8 64.140.112.189   22ms  20ms  21ms
        9  38.122.69.129   22ms  21ms  21ms
       10   154.54.42.90   31ms  28ms  48ms
       11  154.54.45.118   55ms  37ms  26ms
       12 38.104.154.234   27ms  27ms  34ms
       13 77.243.185.220   38ms  45ms  38ms
       14  92.243.64.136   25ms  25ms  27ms
    Traceroute for ultra low latency secondary IPv4 (86.106.90.57)
        1    192.168.2.1    0ms   0ms   0ms
        2   198.2.98.193   11ms  10ms  10ms
        3  104.153.24.70   15ms  14ms  23ms
        4  104.153.24.69   34ms  15ms  18ms
        5 64.140.112.173   17ms  18ms  17ms
        6 64.140.112.172   26ms  15ms  17ms
        7 64.140.112.168   18ms  16ms  16ms
        8 64.140.112.152   21ms  18ms  17ms
        9 64.140.112.117   20ms  19ms  17ms
       10  216.66.14.129    *     *    21ms
       11 184.104.197.33   26ms   *     *
       12  198.179.18.86   27ms  27ms  25ms
       13 77.243.185.220   38ms  44ms  28ms
       14  193.9.115.223   25ms  28ms  32ms
       15  45.11.107.159   24ms  26ms  26ms
       16   86.106.90.57   27ms  26ms  29ms
    Traceroute for anycast primary IPv4 (45.90.28.0)
        1    192.168.2.1    0ms   0ms   0ms
        2   198.2.98.193   12ms  23ms 121ms
        3  104.153.24.70   14ms  20ms  15ms
        4  104.153.26.69   19ms  16ms  25ms
        5 64.140.112.173   19ms  20ms  19ms
        6 64.140.112.172   16ms  24ms  24ms
        7 64.140.112.168   18ms  15ms  15ms
        8 64.140.112.152   15ms  20ms  16ms
        9 64.140.112.117   24ms  22ms  20ms
       10 206.108.35.117   17ms  18ms  25ms
       11     10.83.0.66   20ms  21ms  20ms
       12     10.83.0.42   17ms  19ms  18ms
       13                   *     *     *
       14                   *     *     *
       15                   *     *     *
       16                   *     *     *
       17                   *     *     *
       18                   *     *     *
       19                   *     *     *
       20                   *     *     *
    Traceroute for anycast secondary IPv4 (45.90.30.0)
        1    192.168.2.1    0ms   0ms   0ms
        2   198.2.98.193   10ms  10ms  10ms
        3  104.153.24.70   15ms  20ms  14ms
        4  104.153.26.69   25ms  30ms  16ms
        5 64.140.112.173   16ms  16ms  87ms
        6 64.140.112.172   39ms  21ms  59ms
        7 64.140.112.168   41ms  22ms  19ms
        8 64.140.112.152   18ms  18ms  14ms
        9 64.140.112.117   19ms  21ms  19ms
       10  206.108.35.71   17ms  19ms  20ms
       11                   *     *     *
       12                   *     *     *
       13                   *     *     *
       14                   *     *     *
       15                   *     *     *
       16                   *     *     *
       17                   *     *     *
       18                   *     *     *
       19                   *     *     *
       20                   *     *     *
    Do you want to send this report? [Y/n]:
    Optional email in case we need additional info:
    Post unsuccessful: status 400
    {"error":"0: instance.Test requires property \"Client\"\n"}
    
    • Peter_J
    • 6 mths ago
    • Reported - view

    Looks like a little bit of time in the penalty box was all it needed. I guess this can be closed.

Content aside

  • 6 mths agoLast active
  • 2Replies
  • 84Views
  • 1 Following