0

NextDNS seems to think my current ISP is based in the US

Most (if not all) of DNS answers I receive for services that are geo aware are pointing me to US located IPs tho I'm based in Belgium. Thus making the whole experience sluggish as having to reach the other side of the world.

The AS of my ISP is AS47377.

Tested with multiple profiles and against different transports.

8 replies

null
    • Xavier
    • 4 mths ago
    • Reported - view

    @nextdns ?

    • NextDNs
    • 4 mths ago
    • Reported - view

    Please provide a https://nextdns.io/diag

    • Xavier
    • 4 mths ago
    • Reported - view

    Times out at hop 5 on second ipv4

    Welcome to NextDNS network diagnostic tool.

    This tool will download a small binary to capture latency and routing information
    regarding the connectivity of your network with NextDNS. In order to perform a
    traceroute, root permission is required. You may therefore be asked to provide
    your password for sudo.

    The source code of this tool is available at https://github.com/nextdns/diag

    Do you want to continue? (press enter to accept)
    Testing IPv6 connectivity
      available: true
    Fetching https://test.nextdns.io
      status: unconfigured
      client: 2a01:cc00:2:208::7
      resolver: 176.58.93.85
    Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
      zepto-ams: 15.739ms
    Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
      vultr-ams: 17.853ms
    Fetching PoP name for anycast primary IPv4 (45.90.28.0)
      vultr-ams: 12.329ms
    Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
      vultr-ams: 16.665ms
    Fetching PoP name for ultra low latency primary IPv6 (ipv6.dns1.nextdns.io)
      zepto-ams: 14.761ms
    Fetching PoP name for ultra low latency secondary IPv6 (ipv6.dns2.nextdns.io)
      vultr-ams: 15.345ms
    Fetching PoP name for anycast primary IPv6 (2a07:a8c0::)
      vultr-ams: 12.681ms
    Fetching PoP name for anycast secondary IPv6 (2a07:a8c1::)
      vultr-ams: 18.088ms
    Pinging PoPs
      zepto-bru (IPv6): 11.554ms
      zepto-bru: 11.538ms
      fusa-bru: 17.89ms
      zepto-ams: 17.964ms
      vultr-ams (IPv6): 17.929ms
      zepto-ams (IPv6): 17.88ms
      zepto-ams: 17.893ms
      zepto-ams (IPv6): 17.966ms
      vultr-ams: 17.955ms
      anexia-lux (IPv6): 18.055ms
      fusa-bru (IPv6): 18.353ms
      anexia-lux: 17.944ms
      virtua-par: 18.169ms
      anexia-par: 20.461ms
      netbarista-par: 18.325ms
      netbarista-par (IPv6): 23.933ms
      anexia-par (IPv6): 21.309ms
      anexia-ams: 24.152ms
      virtua-par (IPv6): 24.036ms
      anexia-ams (IPv6): 29.825ms
    Traceroute for ultra low latency primary IPv4 (45.11.106.155)
        1    10.133.44.1   10ms   9ms  11ms
        2 212.68.211.142   12ms  13ms  17ms
        3 212.224.245.178   15ms  13ms  15ms
        4 212.224.245.177   12ms  15ms  11ms
        5  81.52.186.121   12ms  11ms  11ms
        6 193.251.241.222   15ms  15ms  14ms
        7 193.251.141.240   15ms  17ms  14ms
        8 45.134.214.137   15ms  14ms  18ms
        9    45.11.106.4   15ms  14ms  14ms
       10  45.11.106.155   14ms  17ms  14ms
    Traceroute for ultra low latency secondary IPv4 (95.179.134.211)
        1    10.133.44.1    9ms  13ms  13ms
        2 212.68.211.142   20ms  12ms  12ms
        3 212.224.245.178   11ms  10ms  10ms
        4 212.224.245.177   11ms  11ms  12ms
        5 213.19.195.193   12ms  13ms  10ms

    • Xavier
    • 4 mths ago
    • Reported - view

    @nextdns ?

      • NextDNs
      • 4 mths ago
      • Reported - view

      what do you get for: 

      curl -L https://test.nextdns.io

      and 

      dig +tcp chaos test.com @45.90.28.0
      • Xavier
      • 4 mths ago
      • Reported - view

       

      ❯ curl -L https://test.nextdns.io
      {
              "status": "ok",
              "protocol": "DOH",
              "profile": "fp034331629a2d0fe0",
              "client": "91.86.<redacted>",
              "srcIP": "91.86.<redacted>",
              "destIP": "38.175.116.128",
              "anycast": false,
              "server": "zepto-bru-1",
              "clientName": "nextdns-cli",
              "deviceName": "Xavier - p2501",
              "deviceID": "MTNF0",
              "deviceIP": "10.31.73.115",
              "deviceModel": "mac:f0:2f:74"
      }

      ❯ dig +tcp chaos test.com @45.90.28.0
      ;; Warning: Message parser reports malformed message packet.

      ; <<>> DiG 9.18.27 <<>> +tcp chaos test.com @45.90.28.0
      ;; global options: +cmd
      ;; Got answer:
      ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33056
      ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 7

      ;; OPT PSEUDOSECTION:
      ; EDNS: version: 0, flags:; udp: 1232
      ;; QUESTION SECTION:
      ;test.com.                      CH      A

      ;; ANSWER SECTION:
      test.com. 214 IN A 3.18.255.247
      test.com. 214 IN A 34.224.149.186

      ;; ADDITIONAL SECTION:
      client-name.nextdns.io. 0 CH TXT "unknown"
      proto.nextdns.io. 0 CH TXT "TCP"
      server.nextdns.io. 0 CH TXT "vultr-ams-1"
      profile.nextdns.io. 0 CH TXT "default"
      client.nextdns.io. 0 CH TXT "91.86.44.74"
      smart-ecs.nextdns.io. 0 CH TXT "not sent"

      ;; Query time: 16 msec
      ;; SERVER: 45.90.28.0#53(45.90.28.0) (TCP)
      ;; WHEN: Tue May 28 17:06:11 CEST 2024
      ;; MSG SIZE  rcvd: 320

      • Xavier
      • 4 mths ago
      • Reported - view

      @NextDNS ?

    • Xavier
    • 4 mths ago
    • Reported - view

    Not sure what y'all did but it's fixed since at least yesterday.

    Thanks 👍

Login to reply

Content aside

  • 4 mths agoLast active
  • 8Replies
  • 180Views
  • 2 Following