Download, Latency or Ping Times have Slowed Down since Turning on Live Parental Controls

Follow

Comments

23 comments

  • Avatar
    bollegroup

    I am on a fiber to home connection and before OpenDNS I was getting 25 Mb/s now I am down to 7 Mb/s

  • Avatar
    rotblitz

    It seems your understanding about DNS is not sufficient enough to see that DNS is hardly related to download speed.  DNS is the phone book of the internet, not the phone lines.

    Whatever, if you're not convinced, go back to the previously used DNS service to verify that the download speed returns to 25 Mb/s again.  If it doesn't, it's not OpenDNS.

  • Avatar
    kadian78

    actually dns can effect throughput it all depends on where the traffic is being directed to.

  • Avatar
    rotblitz

    Yes, we know.  And this again depends on your Geo location and the one of the DNS service you use.

    So, if you're using a far distance DNS service, you may get provided with IP address information of far distance services.  You can check what OpenDNS data center location you're using, if at all:

       nslookup -type=txt which.opendns.com.

  • Avatar
    tahquitz

    Roblitz is the type of tech that exhibits a superior attitude when responding to a question, with the apparent goal to either showing his superior knowledge, or showing the other persons apparent ignorance under the guise of trying to help. Hopefully, he is NOT in tech support. He is not the type of person I would hire for tech support and I do hire tech support people. He may be right, but I would ignore any more comments from him, if I were you. He does not represent what good tech support offers.

  • Avatar
    mytesla

    We are noticing latency delay with OPENDNS, we are regularly getting over 1000ms ping. Sometimes it is so slow that the web browser times out. I love the parental control but it is just too slow. It used to be fast, I do not know what happened.

  • Avatar
    eric

    Agreed, I have been using OpenDNS (208.67.222.222 / 208.67.220.220) for about 5 years, and in the last 1-2 weeks, it has slowed down BEYOND QUESTION.

    There's a huge problem over there.  What happened?

    This service used to be awesome.  Now, in the last 2 weeks, it stinks.

    What's up?

  • Avatar
    rotblitz

    If you think it is OpenDNS (LPC), copy & paste the complete plain text outputs of the following diagnostic commands to here, so that I can take a look what it may be.

    nslookup -type=txt debug.opendns.com.
    nslookup whoami.akamai.net.
    tracert 208.67.222.222
    tracert 208.67.220.220

     

  • Avatar
    lilikoi

    rotblitz,

    I'm experiencing longer than usual latency too lately. I've reset modem and router and am starting to suspect it is OpenDNS, which is what brought me to this thread. I don't believe I'm using LPC though.I just use OpenDNS to manage my home network with custom content filtering.

    I'll gladly run those commands if you think they'll be relevant to my case.

     

    Thanks

  • Avatar
    rotblitz

    Without seeing the command outputs it is hard to say if they are relevant to your case.

  • Avatar
    dag.findalfossmo

    Same problem here (Oslo, Norway):


    nslookup -type=txt debug.opendns.com :



    Server: 10.0.1.1

    Address: 10.0.1.1#53




    Non-authoritative answer:

    debug.opendns.com text = "server m25.lon"

    debug.opendns.com text = "flags 20 0 50 39500007E00400014C3"

    debug.opendns.com text = "originid 22451487"

    debug.opendns.com text = "actype 2"

    debug.opendns.com text = "bundle 6246751"

    debug.opendns.com text = "source 46.9.202.70:41175"




    Authoritative answers can be found from:



    $ nslookup whoami.akamai.net.


    Server: 10.0.1.1

    Address: 10.0.1.1#53




    Non-authoritative answer:

    Name: whoami.akamai.net

    Address: 208.69.34.69

    traceroute 208.67.222.222

    traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 52 byte packets

    1  10.0.1.1 (10.0.1.1)  2.096 ms  1.106 ms  1.026 ms

    2  10.133.192.1 (10.133.192.1)  8.538 ms  27.652 ms  15.480 ms

    3  193.212.177.233 (193.212.177.233)  10.328 ms  19.163 ms  14.016 ms

    4  ti0001c360-ae45-0.ti.telenor.net (146.172.101.113)  65.278 ms  50.244 ms  43.851 ms

    5  ti3004c400-ae5-0.ti.telenor.net (146.172.100.38)  42.636 ms  46.045 ms  62.552 ms

    6  ti9002b400-ae3-0.ti.telenor.net (146.172.105.6)  43.123 ms  61.268 ms  43.210 ms

    7  gi0-0p226.rtr1.lon.opendns.com (195.66.237.70)  50.026 ms  52.047 ms  47.253 ms

    8  resolver1.opendns.com (208.67.222.222)  44.556 ms  48.665 ms  45.717 ms

    $ traceroute 208.67.220.220

    traceroute to 208.67.220.220 (208.67.220.220), 64 hops max, 52 byte packets

    1  10.0.1.1 (10.0.1.1)  6.444 ms  1.159 ms  1.182 ms

    2  10.133.192.1 (10.133.192.1)  7.702 ms  10.658 ms  12.189 ms

    3  193.212.177.233 (193.212.177.233)  10.892 ms  9.319 ms  28.203 ms

    4  ti0001c360-ae45-0.ti.telenor.net (146.172.101.113)  65.118 ms  50.222 ms  48.226 ms

    5  ti3004c400-ae5-0.ti.telenor.net (146.172.100.38)  44.927 ms  65.335 ms *

    6  ti9002b400-ae3-0.ti.telenor.net (146.172.105.6)  44.779 ms  48.546 ms  44.224 ms

    7  gi0-0p226.rtr1.lon.opendns.com (195.66.237.70)  48.980 ms  46.940 ms  48.440 ms

    8  resolver2.opendns.com (208.67.220.220)  47.075 ms  52.810 ms  49.490 ms
  • Avatar
    rotblitz

    Your ISP and their peering network carriers have configured suboptimal routing for OpenDNS' anycast resolver addresses.  They route you to the London DC although Copenhagen DC may be better for you.  The effect is not only that your DNS latency is around 50ms which should be around 20ms, you also will get suboptional IP address information returned for geolocation dependent internet services, related to the UK instead of Scandinavia.

    You may open a support ticket with OpenDNS, so that they can try to work with your ISP and the network carriers to get the routing optimized, and you can contact your ISP too.

  • Avatar
    piroshki

    Hum. I am also having problems, which have started about two weeks ago. Without parental controls my network is screamingly fast. With, things become erratic. Here is what I get if I do a trace route on the DNS servers.

    nslookup -type=txt debug.opendns.com.

    Server: 192.168.1.1

    Address: 192.168.1.1#53

     

    Non-authoritative answer:

    debug.opendns.com text = "server m8.nyc"

    debug.opendns.com text = "device 0000F1F69D0B77F6"

    debug.opendns.com text = "flags 422 0 8010 3940000000000000000"

    debug.opendns.com text = "originid 100883167"

    debug.opendns.com text = "actype 1"

    debug.opendns.com text = "bundle 100883167"

    debug.opendns.com text = "source 68.1.166.115:39969"

     

    Authoritative answers can be found from:

     

    Thomass-iMac:~ tom$ nslookup whoami.akamai.net.

    Server: 192.168.1.1

    Address: 192.168.1.1#53

     

    Non-authoritative answer:

    Name: whoami.akamai.net

    Address: 208.67.217.18

    traceroute 208.67.222.222

    traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 52 byte packets

     1  192.168.1.1 (192.168.1.1)  5.307 ms  1.794 ms  2.683 ms

     2  10.2.48.1 (10.2.48.1)  11.167 ms  11.926 ms  9.928 ms

     3  ip98-190-33-125.ri.ri.cox.net (98.190.33.125)  12.881 ms  13.478 ms  12.167 ms

     4  ip98-190-33-125.ri.ri.cox.net (98.190.33.125)  13.996 ms  13.678 ms  13.495 ms

     5  nyrkbprj01-ae3.0.rd.ny.cox.net (68.1.5.157)  17.501 ms  17.804 ms  17.481 ms

     6  lag-22.ear2.newyork1.level3.net (4.35.90.1)  42.769 ms  19.968 ms  17.788 ms

     7  * * *

     8  open-dns-in.ear3.newyork1.level3.net (4.78.132.22)  24.306 ms  17.076 ms  17.174 ms

     9  resolver1.opendns.com (208.67.222.222)  18.352 ms  18.570 ms  17.276 ms

     

    traceroute 208.67.222.220

    traceroute to 208.67.222.220 (208.67.222.220), 64 hops max, 52 byte packets

     1  192.168.1.1 (192.168.1.1)  390.825 ms  5.301 ms  8.331 ms

     2  10.2.48.1 (10.2.48.1)  15.376 ms  11.680 ms  13.350 ms

     3  ip98-190-33-123.ri.ri.cox.net (98.190.33.123)  35.067 ms  25.697 ms  11.160 ms

     4  ip98-190-33-123.ri.ri.cox.net (98.190.33.123)  11.376 ms  15.035 ms  17.357 ms

     5  nyrkbprj01-ae3.0.rd.ny.cox.net (68.1.5.157)  27.100 ms  19.697 ms  39.967 ms

     6  lag-22.ear2.newyork1.level3.net (4.35.90.1)  20.940 ms  1295.792 ms  102.646 ms

     7  * * *

     8  open-dns-in.ear3.newyork1.level3.net (4.78.132.22)  32.375 ms  17.743 ms  17.790 ms

     9  resolver3.opendns.com (208.67.222.220)  18.757 ms  21.557 ms  24.723 ms

     

    Looks like level 3 is part of the problem?

     

    P.

     

  • Avatar
    piroshki

    Yup, as or right now Level3 is having problems. Perhaps this is why I am having issues with OpenDNS?

     

    P.

     

    Check out: http://downdetector.com/status/level3/map/

  • Avatar
    rotblitz

    Well, according to your outputs you do not have DNS problems.  You're located around Wakefield and are routed to the closest OpenDNS DC in NYC.  Your DNS latency is in the expected range of 20ms.

    You may have speed problems, with Level-3 as you found out.  Best would be to perform a speed test, e.g. with http://www.speedtest.net/ 
    Please note, speed problems are usually not related to DNS if you're routed correctly as in your case and if you get your DNS queries quickly responded to.  You also can test the DNS response times with a Windows tool like https://www.grc.com/dns/benchmark.htm or with the dig command on your Mac.

  • Avatar
    mr.tim

    I am wondering if I can request help / feedback from someone at OpenDNS.  I believe I have noted this problem recently / in the last few weeks,

     

    - OpenDNS lookups used to be consistently fast and reliable / for >1 year of use

    - in the last month, I have found things intermittently range from "good" to "slow" to "utterly unusable" (ie, DNS fails to resolve things that resolve fine when I use different DNS provider like GoogleDNS @ 8.8.8.8)

    - for reference I am putting output below / which was asked for earlier in this thread / which I believe gives some hints about the route / my ISP / to OpenDNS services.

     

    If there is any other info I can provide to help make it clear what might be awry, your comments/suggestions are greatly appreciated.

     

    Thanks!

    Tim

     

    --paste--

     

    nslookup -type=txt debug.opendns.com.
    nslookup whoami.akamai.net.
    tracert 208.67.222.222
    tracert 208.67.220.220

    TELLS ME:


    root@proxmox:~# cat /etc/resolv.conf
    nameserver 208.67.220.220
    nameserver 208.67.222.222

    root@proxmox:~#
    root@proxmox:~#
    root@proxmox:~# nslookup -type=txt debug.opendns.com.
    Server:         208.67.220.220
    Address:        208.67.220.220#53

    Non-authoritative answer:
    debug.opendns.com       text = "server m33.yyz"
    debug.opendns.com       text = "flags 20 0 50 39500007E00400014C3"
    debug.opendns.com       text = "originid 108423769"
    debug.opendns.com       text = "actype 2"
    debug.opendns.com       text = "bundle 10441517"
    debug.opendns.com       text = "source 47.55.140.23:52665"

    Authoritative answers can be found from:

    root@proxmox:~# nslookup whoami.akamai.net.
    Server:         208.67.222.222
    Address:        208.67.222.222#53

    Non-authoritative answer:
    Name:   whoami.akamai.net
    Address: 67.215.84.64

    root@proxmox:~# tracert 208.67.222.222
    -bash: tracert: command not found
    root@proxmox:~# tracert 208.67.220.220
    -bash: tracert: command not found
    root@proxmox:~# traceroute 208.67.222.222
    traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets
     1  192.168.143.34 (192.168.143.34)  0.437 ms  0.586 ms  0.717 ms
     2  loop0.7vw.ba18.hlfx.ns.aliant.net (142.176.50.20)  3.065 ms  3.116 ms  3.250 ms
     3  ae13-182.cr02.hlfx.ns.aliant.net (142.166.181.21)  3.341 ms  3.393 ms be12-181.cr01.hlfx.ns.aliant.net (142.166.181.17)  5.352 ms
     4  be16.cr01.stjh.nb.aliant.net (142.166.185.65)  6.494 ms hg-0-2-0-0-50.cr01.hlfx.ns.aliant.net (142.166.149.93)  4.629 ms  4.682 ms
     5  et-5-1-0-50.cr02.drmo.ns.aliant.net (142.166.218.66)  3.433 ms be16.cr01.stjh.nb.aliant.net (142.166.185.65)  6.532 ms ae3-50.cr02.stjh.nb.aliant.net (142.166.181.110)  6.074 ms
     6  ae3-50.cr02.stjh.nb.aliant.net (142.166.181.110)  11.774 ms  4.126 ms  7.846 ms
     7  ae4.cr02.stjh.nb.aliant.net (142.166.129.65)  8.181 ms ae0.bx01.toro.on.aliant.net (207.231.227.53)  25.754 ms bx2-torontoxn_ae3 (184.150.187.56)  38.147 ms
     8  ae0.bx01.toro.on.aliant.net (207.231.227.53)  25.853 ms  25.794 ms bx2-torontoxn_ae3 (184.150.187.56)  38.489 ms
     9  tcore3-toronto12_bundle-ether23.net.bell.ca (64.230.51.149)  36.970 ms tcore3-torontoxn_hundredgige0-6-0-0.net.bell.ca (64.230.97.144)  36.251 ms bx2-torontoxn_ae3 (184.150.187.56)  38.524 ms
    10  tcore3-torontoxn_hundredgige0-6-0-0.net.bell.ca (64.230.97.144)  36.244 ms tcore4-toronto47_bundle-ether31.net.bell.ca (64.230.51.159)  42.029 ms tcore4-toronto01_0-1-0-1.net.bell.ca (64.230.50.236)  41.372 ms
    11  tcore4-toronto01_0-1-0-1.net.bell.ca (64.230.50.236)  41.373 ms tcore3-toronto12_bundle-ether23.net.bell.ca (64.230.51.149)  36.930 ms tcore4-toronto01_100gige0-14-0-0.net.bell.ca (64.230.50.81)  39.692 ms
    12  bx2-toronto01_et7-1-0.net.bell.ca (64.230.109.143)  34.218 ms  32.730 ms tcore4-toronto01_0-1-0-1.net.bell.ca (64.230.50.236)  37.502 ms
    13  ae55.bar2.Toronto1.Level3.net (4.28.138.45)  29.426 ms ae-0-11.bar1.Toronto1.Level3.net (4.69.151.241)  29.292 ms  29.223 ms
    14  OPEN-DNS-IN.bar1.Toronto1.Level3.net (4.28.142.178)  34.507 ms  34.439 ms ae-0-11.bar1.Toronto1.Level3.net (4.69.151.241)  29.318 ms
    15  ae-0-11.bar1.Toronto1.Level3.net (4.69.151.241)  28.221 ms OPEN-DNS-IN.bar1.Toronto1.Level3.net (4.28.142.178)  34.018 ms  34.438 ms
    16  resolver1.opendns.com (208.67.222.222)  34.329 ms  34.494 ms  34.251 ms
    root@proxmox:~# traceroute 208.67.220.220
    traceroute to 208.67.220.220 (208.67.220.220), 30 hops max, 60 byte packets
     1  192.168.143.34 (192.168.143.34)  0.522 ms  0.685 ms  0.890 ms
     2  loop0.7vw.ba18.hlfx.ns.aliant.net (142.176.50.20)  6.846 ms  6.790 ms  6.729 ms
     3  ae13-182.cr02.hlfx.ns.aliant.net (142.166.181.21)  6.662 ms be12-181.cr01.hlfx.ns.aliant.net (142.166.181.17)  7.265 ms  7.309 ms
     4  hg-0-2-0-0-50.cr01.hlfx.ns.aliant.net (142.166.149.93)  7.135 ms hg-0-4-0-0.cr01.drmo.ns.aliant.net (142.166.211.74)  7.393 ms hg-0-2-0-0-50.cr01.hlfx.ns.aliant.net (142.166.149.93)  7.182 ms
     5  ae3-50.cr02.stjh.nb.aliant.net (142.166.181.110)  9.711 ms hg-0-4-0-0.cr01.drmo.ns.aliant.net (142.166.211.74)  7.430 ms  7.473 ms
     6  ae4.cr02.stjh.nb.aliant.net (142.166.129.65)  9.928 ms  4.530 ms  4.895 ms
     7  ae0.bx01.toro.on.aliant.net (207.231.227.53)  22.487 ms ae4.cr02.stjh.nb.aliant.net (142.166.129.65)  4.929 ms  4.971 ms
     8  ae0.bx01.toro.on.aliant.net (207.231.227.53)  22.519 ms tcore4-torontoxn_hundredgige0-6-0-0.net.bell.ca (64.230.97.146)  32.804 ms tcore3-torontoxn_hundredgige0-6-0-0.net.bell.ca (64.230.97.144)  39.090 ms
     9  tcore4-torontoxn_hundredgige0-6-0-0.net.bell.ca (64.230.97.146)  38.534 ms tcore4-toronto21_bundle-ether23.net.bell.ca (64.230.51.163)  42.618 ms tcore4-torontoxn_hundredgige0-6-0-0.net.bell.ca (64.230.97.146)  38.514 ms
    10  tcore3-toronto12_bundle-ether23.net.bell.ca (64.230.51.149)  42.923 ms tcore4-toronto01_0-1-0-1.net.bell.ca (64.230.50.236)  47.152 ms tcore3-torontoxn_hundredgige0-6-0-0.net.bell.ca (64.230.97.144)  39.059 ms
    11  tcore4-toronto21_bundle-ether23.net.bell.ca (64.230.51.163)  42.592 ms  42.588 ms bx2-toronto01_et7-1-0.net.bell.ca (64.230.109.143)  39.068 ms
    12  bx2-toronto01_et5-1-0.net.bell.ca (64.230.109.141)  36.584 ms ae55.bar2.Toronto1.Level3.net (4.28.138.45)  23.963 ms bx2-toronto01_et7-1-0.net.bell.ca (64.230.109.143)  34.229 ms
    13  bx2-toronto01_et5-1-0.net.bell.ca (64.230.109.141)  37.627 ms bx2-toronto01_et7-1-0.net.bell.ca (64.230.109.143)  33.101 ms  33.138 ms
    14  ae-0-11.bar1.Toronto1.Level3.net (4.69.151.241)  23.053 ms  22.850 ms  23.100 ms
    15  ae-0-11.bar1.Toronto1.Level3.net (4.69.151.241)  29.565 ms OPEN-DNS-IN.bar1.Toronto1.Level3.net (4.28.142.178)  34.855 ms  34.766 ms
    16  * resolver2.opendns.com (208.67.220.220)  35.244 ms  34.779 ms



    For reference, my ISP is "Aliant/Bell FibreOP / Fibe service".  I've got some other clients in town who also use FibreOp-Aliant and they appear to now be experiencing similar intermittent issues, ie, suggests maybe something in route/ISP config is sub-par?  I have some other clients who use the other local main ISP (Eastlink, who deploy cable modems to client sites) - and I don't think I have ever seen any problems with those clients and OpenDNS. Despite being geographically in similar part of the country (ie, Halifax NS Canada)

     

    Thanks!

  • Avatar
    rotblitz

    There's nothing bad from your outputs.

  • Avatar
    mr.tim

    Thanks for the feedback! Greatly appreciated.  I will try now, just 'for fun' - reverting back to using openDNS on my laptop / and next time I notice DNS timeouts-fails / 'internet being broken' I will re-do the same CLI tests and see if things look differently or not from this 'good' reference state.  Thanks for your help! -T

  • Avatar
    rotblitz

    Well, 'good' state is relative only.  Your ping to OpenDNS is about 35ms.  Normal would be 20ms.

    Your ISP routes traffic for the OpenDNS anycast addresses to the OpenDNS DC in Toronto although New York may be closer.


    This may be with the intention to keep the traffic in the country, no idea.

  • Avatar
    mr.tim

    Sigh, this is weird.  DNS just had a flip out a few minutes ago (ie, more accurately, my ability to query OpenDNS was temporarily broken).

    I re-ran the 4 diagnostic commands, and the first one returned a fail/timeout; the others appear? to be more or less unchanged.

    About 10 minutes later it no longer is having this problem.

    Not sure if this gives any indication of what the transitory issue was / or what more info I need to try to capture when things are broken?

    --paste--

    FAILING PROBLEM:


    root@proxmox:~# !493
    nslookup -type=txt debug.opendns.com. ; nslookup whoami.akamai.net. ; traceroute 208.67.222.222 ; traceroute 208.67.220.220
    ;; connection timed out; no servers could be reached

    Server:         208.67.222.222
    Address:        208.67.222.222#53

    Non-authoritative answer:
    Name:   whoami.akamai.net
    Address: 67.215.84.64

    traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets
     1  192.168.143.34 (192.168.143.34)  0.302 ms  0.447 ms  0.577 ms
     2  142.176.50.20 (142.176.50.20)  4.702 ms  4.749 ms  4.619 ms
     3  ae13-182.cr02.hlfx.ns.aliant.net (142.166.181.21)  6.314 ms  6.252 ms be12-181.cr01.hlfx.ns.aliant.net (142.166.181.17)  6.032 ms
     4  142.166.185.65 (142.166.185.65)  10.027 ms 142.166.211.74 (142.166.211.74)  6.102 ms 142.166.185.65 (142.166.185.65)  9.942 ms
     5  be16.cr01.stjh.nb.aliant.net (142.166.185.65)  10.061 ms 142.166.218.66 (142.166.218.66)  4.764 ms hg-0-4-0-0.cr01.drmo.ns.aliant.                                  net (142.166.211.74)  6.135 ms
     6  ae0.bx01.toro.on.aliant.net (207.231.227.53)  25.334 ms et-5-1-0-50.cr02.drmo.ns.aliant.net (142.166.218.66)  1.257 ms  6.852 ms
     7  ae0.bx01.toro.on.aliant.net (207.231.227.53)  27.758 ms bx2-torontoxn_ae3 (184.150.187.56)  39.989 ms ae0.bx01.toro.on.aliant.net                                   (207.231.227.53)  27.802 ms
     8  64.230.97.146 (64.230.97.146)  37.921 ms ae0.bx01.toro.on.aliant.net (207.231.227.53)  27.849 ms 184.150.187.56 (184.150.187.56)  40.158 ms
     9  tcore3-torontoxn_hundredgige0-6-0-0.net.bell.ca (64.230.97.144)  38.254 ms 64.230.51.159 (64.230.51.159)  46.285 ms 64.230.97.146 (64.230.97.146)  37.896 ms
    10  64.230.50.81 (64.230.50.81)  40.128 ms  40.123 ms 64.230.51.159 (64.230.51.159)  46.267 ms
    11  64.230.51.159 (64.230.51.159)  46.263 ms bx2-toronto01_et7-1-0.net.bell.ca (64.230.109.143)  38.728 ms 64.230.50.236 (64.230.50.236)  41.354 ms
    12  ae55.bar2.Toronto1.Level3.net (4.28.138.45)  23.091 ms  23.221 ms tcore4-toronto01_0-1-0-1.net.bell.ca (64.230.50.236)  41.880 ms
    13  ae55.bar2.Toronto1.Level3.net (4.28.138.45)  23.124 ms ae-0-11.bar1.Toronto1.Level3.net (4.69.151.241)  28.800 ms bx2-toronto01_et7-1-0.net.bell.ca (64.230.109.143)  45.672 ms
    14  OPEN-DNS-IN.bar1.Toronto1.Level3.net (4.28.142.178)  35.180 ms ae-0-11.bar1.Toronto1.Level3.net (4.69.151.241)  28.670 ms ae55.bar2.Toronto1.Level3.net (4.28.138.45)  29.163 ms
    15  resolver1.opendns.com (208.67.222.222)  35.241 ms ae-0-11.bar1.Toronto1.Level3.net (4.69.151.241)  28.709 ms resolver1.opendns.com (208.67.222.222)  35.467 ms
    traceroute to 208.67.220.220 (208.67.220.220), 30 hops max, 60 byte packets
     1  192.168.143.34 (192.168.143.34)  0.318 ms  0.476 ms  0.607 ms
     2  loop0.7vw.ba18.hlfx.ns.aliant.net (142.176.50.20)  5.783 ms  6.024 ms  5.706 ms
     3  be12-181.cr01.hlfx.ns.aliant.net (142.166.181.17)  6.189 ms ae13-182.cr02.hlfx.ns.aliant.net (142.166.181.21)  5.837 ms  5.886 ms
     4  hg-0-4-0-0.cr01.drmo.ns.aliant.net (142.166.211.74)  7.520 ms hg-0-2-0-0-50.cr01.hlfx.ns.aliant.net (142.166.149.93)  6.238 ms  6.286 ms
     5  ae3-50.cr02.stjh.nb.aliant.net (142.166.181.110)  8.723 ms hg-0-4-0-0.cr01.drmo.ns.aliant.net (142.166.211.74)  7.553 ms et-5-1-0-50.cr02.drmo.ns.aliant.net (142.166.218.66)  6.055 ms
     6  ae4.cr02.stjh.nb.aliant.net (142.166.129.65)  8.980 ms et-5-1-0-50.cr02.drmo.ns.aliant.net (142.166.218.66)  1.726 ms ae0.bx01.toro.on.aliant.net (207.231.227.53)  21.795 ms
     7  ae4.cr02.stjh.nb.aliant.net (142.166.129.65)  10.101 ms  10.150 ms ae0.bx01.toro.on.aliant.net (207.231.227.53)  27.578 ms
     8  bx2-torontoxn_ae3 (184.150.187.56)  40.714 ms tcore4-torontoxn_hundredgige0-6-0-0.net.bell.ca (64.230.97.146)  38.274 ms bx2-torontoxn_ae3 (184.150.187.56)  40.378 ms
     9  tcore4-torontoxn_hundredgige0-6-0-0.net.bell.ca (64.230.97.146)  38.263 ms bx2-torontoxn_ae3 (184.150.187.56)  40.739 ms tcore3-toronto12_bundle-ether23.net.bell.ca (64.230.51.149)  38.242 ms
    10  tcore4-toronto01_0-1-0-1.net.bell.ca (64.230.50.236)  45.449 ms tcore4-toronto21_bundle-ether23.net.bell.ca (64.230.51.163)  40.669 ms tcore4-torontoxn_hundredgige0-6-0-0.net.bell.ca (64.230.97.146)  38.417 ms
    11  tcore3-toronto01_100gige1-14-0-0.net.bell.ca (64.230.50.79)  40.328 ms bx2-toronto01_et7-1-0.net.bell.ca (64.230.109.143)  37.785 ms bx2-toronto01_et5-1-0.net.bell.ca (64.230.109.141)  34.298 ms
    12  bx2-toronto01_et5-1-0.net.bell.ca (64.230.109.141)  34.798 ms  34.651 ms ae55.bar2.Toronto1.Level3.net (4.28.138.45)  23.156 ms
    13  ae55.bar2.Toronto1.Level3.net (4.28.138.45)  23.005 ms bx2-toronto01_et7-1-0.net.bell.ca (64.230.109.143)  32.523 ms ae55.bar2.Toronto1.Level3.net (4.28.138.45)  23.175 ms
    14  ae-0-11.bar1.Toronto1.Level3.net (4.69.151.241)  22.926 ms ae55.bar2.Toronto1.Level3.net (4.28.138.45)  29.152 ms ae-0-11.bar1.Toronto1.Level3.net (4.69.151.241)  28.491 ms
    15  resolver2.opendns.com (208.67.220.220)  34.864 ms  34.810 ms  34.578 ms
    root@proxmox:~#



    FEW MINUTES LATER:

    root@proxmox:~# nslookup -type=txt debug.opendns.com.
    Server:         208.67.220.220
    Address:        208.67.220.220#53

    Non-authoritative answer:
    debug.opendns.com       text = "server m29.yyz"
    debug.opendns.com       text = "flags 20 0 50 39500007E00400014C3"
    debug.opendns.com       text = "originid 108423769"
    debug.opendns.com       text = "actype 2"
    debug.opendns.com       text = "bundle 10441517"
    debug.opendns.com       text = "source 47.55.140.23:50658"

    Authoritative answers can be found from:

    root@proxmox:~#


    10 minutes later -- seems ok now.

  • Avatar
    rotblitz

    Well, this rather looks like intermittent fluctuations of your internet connection, not necessarily a DNS problem.  With the first command you didn't have internet connenction, but from the second command you had.  This is difficult to troubleshoot.

  • Avatar
    mr.tim

    Hi, yes, thanks for the feedback. I agree it is difficult to troubleshoot.  I neglected to explicitly mention,

    -- then the DNS fails (as per the sample above) due to timeout

    -- I can still do things that do not depend on DNS (for example, "ping 8.8.8.8" works just fine; but "ping google.com" will fail; or if I do a DIG DNS lookup against a different (numeric designated) DNS server, such as 8.8.8.8 then this works fine also.

    -- so it appears to be an intermittent fail on DNS traffic specifically, from my ISP to OpenDNS DNS servers, and thus anything that depends on this DNS looking-up also tends to suffer.

     

    I have adjusted my config so my LAN devices don't directly use DNS against openDNS; but rather then point to the 'edge firewall' which is a DNS Cache proxy.  Thus if there is suitably recent DNS records cached locally, then local systems don't notice the DNS breaking temporarily.  But if a fresh DNS lookup is required / then the firewall is polling to OpenDNS servers for lookups / this is what is broken temporarily and intermittently // and things again suffer.  Possibly I need to just setup a local DNS cache which has a longer retention time / for a very large number of records / so that I am better buffered than by the DNS cache on my edge firewall (over which I have really very little control, it is just the unit provided by my ISP).

     

    If there are other workarounds you might recommend I am interested/happy to hear.  Or other things I can/should try to do for debugging, I am happy to do more detailed poking at the problem.

    Thanks for the help!

    Tim

     

  • Avatar
    rotblitz

    You can run the diagnostics from https://support.opendns.com/hc/en-us/articles/227988487 
    Then you open a support ticket with OpenDNS with the link to your diagnostic results and a problem description.  (Don't post it here.  We other users do not have access to it.)

Please sign in to leave a comment.