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

Follow

Comments

15 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.

Please sign in to leave a comment.