0

Telekom Germany slow

Hi, dns responses from German Telekom are slow. Is this really the fastest routing?

traceroute to 45.90.28.200 (45.90.28.200), 64 hops max, 52 byte packets
 1  fritz.box (192.168.178.1)  11.704 ms  2.722 ms  3.783 ms
2 p3e9bf28c.dip0.t-ipconnect.de (62.155.242.141) 6.972 ms 7.692 ms 7.862 ms
3 d-ed5-i.d.de.net.dtag.de (217.5.91.118) 20.733 ms 20.928 ms 22.260 ms
 4  4.68.71.113 (4.68.71.113)  24.102 ms  30.688 ms  28.580 ms
 5  * * *
6 choopa-llc.ear3.amsterdam1.level3.net (213.19.196.242) 48.383 ms 34.123 ms 33.566 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
^C

11replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Like
  • Fetching https://test.nextdns.io
      Fetch error: Get "https://bvpi587g5jiq0q0kt6tg.test.nextdns.io/": read tcp [2003:eb:3f0d:9b00:a879:42d3:ba60:8769]:58464->[2a00:11c0:e:ffff:1::d]:443: read: operation timed out
    Traceroute for primary IPv4 (45.90.28.0)
        1  192.168.178.1    9ms   1ms   2ms
        2 62.155.242.140    7ms   8ms   5ms
        3   217.0.154.10   18ms  16ms  17ms
        4    4.68.71.113   27ms  18ms  20ms
        5                   *     *     *
        6 213.19.196.242   43ms  33ms  32ms
        7                   *     *     *
        8                   *     *     *
        9                   *     *     *
       10     45.90.28.0   36ms  24ms  25ms
    Traceroute for secondary IPv4 (45.90.30.0)
        1  192.168.178.1    4ms   2ms   2ms
        2 62.155.242.140    6ms   6ms   5ms
        3  62.154.17.162  106ms  15ms  15ms
        4 213.248.93.186   17ms  15ms  15ms
        5  62.115.14.117   18ms  17ms  16ms
        6     45.90.30.0   17ms  15ms  15ms
    Traceroute for primary IPv6 (2a07:a8c0::)
        1 2003:eb:3f0d:9b00:464e:6dff:fea4:b517    3ms   3ms   2ms
        2 2003:0:8804:5800::1    8ms   6ms   6ms
        3 2003:0:1304:802a::2   23ms  15ms  15ms
        4 2a01:4a0:1338:134::2   16ms  19ms  28ms
        5 2a02:6ea0:4:1140:5390::2   17ms  21ms  17ms
        6    2a07:a8c0::   17ms  14ms  14ms
    Traceroute for secondary IPv6 (2a07:a8c1::)
        1 2003:eb:3f0d:9b00:464e:6dff:fea4:b517    2ms   2ms   *
        2 2003:0:8804:5800::1   16ms   5ms   7ms
        3 2003:0:130e:17::2   19ms  17ms  17ms
        4 2001:470:0:512::1   15ms  15ms  13ms
        5                   *     *     *
        6                   *     *     *
        7 2001:470:0:410::2    *    45ms  35ms
        8 2001:470:0:440::1  105ms 104ms 108ms
        9 2001:470:0:357::2  102ms 101ms 101ms
       10 2001:470:0:277::1  113ms 103ms 103ms
       11 2001:504:0:2:0:5:7695:1  101ms 102ms 101ms
       12 2a0b:4342:1a30::10  103ms 103ms 102ms
       13    2a07:a8c1::  102ms 101ms 100ms
    Fetching PoP name for primary IPv4 (45.90.28.0)
      vultr-ams: 33.665ms
    Fetching PoP name for secondary IPv4 (45.90.30.0)
      anexia-fra: 16.598ms
    Fetching PoP name for primary IPv6 (2a07:a8c0::)
      zepto-fra: 18.639ms
    Fetching PoP name for secondary IPv6 (2a07:a8c1::)
      zepto-iad: 102.572ms
    Pinging PoPs
     

    Like
  • I run DoT on Fritzbox. 
    It is much faster to run NextDNS on a Server in FRA (with DoT) and use from there DoT in the Fritzbox. Double DoT is faster then NextDNS local. It must be a Routing issue.

    Like
  • Testing IPv6 connectivity
      available: true
    Fetching https://test.nextdns.io
      status: ok
      client: 79.228.2.216
      protocol: DOT
      dest IP: 45.90.30.0
      server: anexia-fra-1
    Traceroute for primary IPv4 (45.90.28.0)
        1  192.168.178.1    2ms   4ms   2ms
        2 62.155.242.140    6ms   7ms   5ms
        3  62.154.43.206   21ms  19ms  22ms
        4    4.68.71.113   20ms  21ms  20ms
        5                   *     *     *
        6 213.19.196.242   56ms  46ms  38ms
        7                   *     *     *
        8                   *     *     *
        9                   *     *     *
       10     45.90.28.0   64ms  57ms  41ms
    Traceroute for secondary IPv4 (45.90.30.0)
        1  192.168.178.1    2ms   4ms   4ms
        2 62.155.242.140   25ms  11ms  14ms
        3  217.5.109.122   29ms  33ms  23ms
        4 213.248.93.186   19ms  19ms  22ms
        5  62.115.14.117   41ms  20ms  24ms
        6     45.90.30.0   27ms  25ms  26ms
    Traceroute for primary IPv6 (2a07:a8c0::)
        1 2003:eb:3f0e:8200:464e:6dff:fea4:b517    2ms   3ms   2ms
        2 2003:0:8804:5800::1    9ms   8ms  26ms
        3 2003:0:1304:802a::2   22ms  28ms  25ms
        4 2a01:4a0:1338:134::2   30ms  17ms  15ms
        5 2a02:6ea0:4:1140:5390::2   16ms  15ms  14ms
        6    2a07:a8c0::   15ms  14ms  16ms
    Traceroute for secondary IPv6 (2a07:a8c1::)
        1 2003:eb:3f0e:8200:464e:6dff:fea4:b517    3ms   2ms   *
        2 2003:0:8804:5800::1    8ms   6ms   6ms
        3 2003:0:130e:17::2   17ms  17ms  15ms
        4 2001:470:0:512::1   31ms  16ms  15ms
        5                   *     *     *
        6                   *     *     *
        7 2001:470:0:410::2   44ms   *    44ms
        8 2001:470:0:440::1  100ms  98ms  98ms
        9 2001:470:0:357::2  103ms 103ms 103ms
       10 2001:470:0:277::1  100ms  99ms 100ms
       11 2001:504:0:2:0:5:7695:1  103ms 102ms 102ms
       12 2a0b:4342:1a30::10  102ms 101ms 101ms
       13    2a07:a8c1::  103ms 101ms 102ms
    Fetching PoP name for primary IPv4 (45.90.28.0)
      vultr-ams: 26.933ms
    Fetching PoP name for secondary IPv4 (45.90.30.0)
      anexia-fra: 16.939ms
    Fetching PoP name for primary IPv6 (2a07:a8c0::)
      zepto-fra: 14.646ms
    Fetching PoP name for secondary IPv6 (2a07:a8c1::)
      zepto-iad: 104.594ms
    Pinging PoPs
    Do you want to send this report? [Y/n]:

    Like
    • Heiko please post the report and provide the report id rather than posting the output.

      Like
Like Follow
  • 9 days agoLast active
  • 11Replies
  • 67Views
  • 2 Following