Support

K-12 Forums

Talk with other K-12 network administrators in your state.

Or see all states.

Categories

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

Domain Name System (DNS) troubles: Bad routing to OpenDNS

Bottom of Page

1 to 17 of 17

  1.  
  1.  permalink
    For some reason, I am getting routed to the EU for my home connection and my linux server hosted at The Planet. Here is a trace from both connections. Is anyone else having these problems? It all started after the Amsterdam site came online.

    li45-41:~# traceroute 208.67.222.222
    traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 40 byte packets
    1 up4.linode.com (67.18.92.3) 0.385 ms 0.487 ms 0.570 ms
    2 po101.dsr02.dllstx2.theplanet.com (70.87.254.77) 17.869 ms 17.854 ms 17.871 ms
    3 te7-4.dsr02.dllstx3.theplanet.com (70.87.253.121) 0.644 ms te9-4.dsr02.dllstx3.theplanet.com (70.87.253.125) 0.721 ms 0.855 ms
    4 et3-1.ibr03.dllstx3.theplanet.com (70.87.253.21) 0.446 ms 0.516 ms 0.564 ms
    5 be.fd.5746.static.theplanet.com (70.87.253.190) 32.447 ms 32.507 ms 32.586 ms
    6 da.ff.5746.static.theplanet.com (70.87.255.218) 106.155 ms 116.707 ms 116.635 ms
    7 gi0-2.rtr1.lon.opendns.com (195.66.225.70) 106.896 ms 106.717 ms 106.869 ms


    Tracing route to resolver1.opendns.com [208.67.222.222]
    over a maximum of 30 hops:

    1 2 ms <1 ms <1 ms 192.168.1.1
    2 72 ms 66 ms 68 ms 68.28.81.69
    3 76 ms 98 ms 85 ms 68.28.81.92
    4 75 ms 90 ms 111 ms 68.28.83.55
    5 * * * Request timed out.
    6 76 ms 74 ms 73 ms 68.28.87.9
    7 * * * Request timed out.
    8 74 ms 64 ms 190 ms 68.28.85.69
    9 74 ms 79 ms 70 ms sl-crs1-kc-0-15-0-0.sprintlink.net [144.223.137.
    225]
    10 89 ms 79 ms 87 ms sl-crs2-chi-0-15-2-0.sprintlink.net [144.232.24.
    206]
    11 210 ms 106 ms 99 ms sl-crs2-nyc-0-8-0-1.sprintlink.net [144.232.20.1
    19]
    12 117 ms 156 ms 108 ms sl-gw35-nyc-15-0-0.sprintlink.net [144.232.13.39
    ]
    13 129 ms 98 ms 106 ms sl-tisca1-288264-0.sprintlink.net [144.223.128.1
    82]
    14 218 ms 196 ms 250 ms xe-7-0-0.ams10.ip4.tinet.net [89.149.185.89]
    15 197 ms 323 ms 186 ms opendns-gw.ip4.tinet.net [77.67.66.70]
    16 202 ms 186 ms 183 ms resolver1.opendns.com [208.67.222.222]

    Trace complete.

    I have tried to do support with OpenDNS with email but they have stop responding to my emails. Here is some more info that they wanted.

    li45-41:~# dig +noall +answer which.opendns.com txt @208.67.222.222
    which.opendns.com. 0 IN TXT "2.lon"

    li45-41:~# dig myip.opendns.com

    ; <<>> DiG 9.5.1-P3 <<>> myip.opendns.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33090
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;myip.opendns.com. IN A

    ;; ANSWER SECTION:
    myip.opendns.com. 0 IN A 72.14.182.41

    ;; Query time: 107 msec
    ;; SERVER: 208.67.222.222#53(208.67.222.222)
    ;; WHEN: Tue Oct 20 09:03:38 2009
    ;; MSG SIZE rcvd: 50
    •  
      CommentAuthordavidu
    • CommentTimeOct 22nd 2009
     permalink
    Administrator
    1) ThePlanet appears to be peering with us in London and not in Dallas. I'll disable their peering in London so traffic flows over transit.

    2) As for sprint, I can try to deal with that now, too.
    •  
      CommentAuthordavidu
    • CommentTimeOct 22nd 2009
     permalink
    Administrator
    We will try to push both these changes tomorrow.
  4.  permalink
    Thank you, forgot to add that my home connection is Sprint but looks like you noticed that :). Both connections use to go to Chicago.

    Thanks again for looking into it.
  5.  permalink
    Changes have been made to ThePlanet all ready, but not with Sprint. Still being routed to Amsterdam on Sprint.
  6.  permalink
    Still not fixed for Sprint..

    Tracing route to resolver1.opendns.com [208.67.222.222]
    over a maximum of 30 hops:

    1 1 ms <1 ms <1 ms 192.168.1.1
    2 224 ms 82 ms 97 ms 68.28.81.69
    3 105 ms 87 ms 80 ms 68.28.81.92
    4 79 ms 96 ms 76 ms 68.28.83.54
    5 94 ms 81 ms 78 ms 68.28.87.5
    6 * * * Request timed out.
    7 100 ms 99 ms 101 ms 68.28.85.69
    8 121 ms 176 ms 80 ms sl-crs1-kc-0-15-0-0.sprintlink.net [144.223.137.
    225]
    9 92 ms 112 ms 118 ms sl-crs1-chi-0-1-0-3.sprintlink.net [144.232.18.2
    14]
    10 115 ms 111 ms 113 ms sl-crs1-chi-0-10-3-0.sprintlink.net [144.232.9.1
    48]
    11 115 ms 111 ms 116 ms sl-gw35-nyc-15-0-0.sprintlink.net [144.232.13.39
    ]
    12 135 ms 132 ms 111 ms sl-tisca1-288264-0.sprintlink.net [144.223.128.1
    82]
    13 211 ms 207 ms 227 ms xe-7-0-0.ams10.ip4.tinet.net [89.149.185.89]
    14 209 ms 206 ms 215 ms opendns-gw.ip4.tinet.net [77.67.66.70]
    15 352 ms 213 ms 212 ms resolver1.opendns.com [208.67.222.222]

    Trace complete.
  7.  permalink
    STILL not fixed for Sprint. Any ETA when this will be fixed?

    Tracing route to resolver1.opendns.com [208.67.222.222]
    over a maximum of 30 hops:

    1 2 ms <1 ms <1 ms 192.168.1.1
    2 68 ms 64 ms 64 ms 68.28.81.69
    3 72 ms 88 ms 93 ms 68.28.81.92
    4 65 ms 194 ms 67 ms 68.28.83.55
    5 * * * Request timed out.
    6 93 ms 82 ms 61 ms 68.28.87.13
    7 * * * Request timed out.
    8 85 ms 93 ms 71 ms 68.28.85.69
    9 75 ms 175 ms 66 ms sl-crs1-kc-0-15-0-0.sprintlink.net [144.223.137.
    225]
    10 85 ms 73 ms 84 ms sl-crs1-chi-0-1-0-3.sprintlink.net [144.232.18.2
    14]
    11 106 ms 99 ms 99 ms sl-crs1-chi-0-10-3-0.sprintlink.net [144.232.9.1
    48]
    12 110 ms 126 ms 120 ms sl-gw35-nyc-15-0-0.sprintlink.net [144.232.13.39
    ]
    13 160 ms 91 ms 125 ms sl-tisca1-288264-0.sprintlink.net [144.223.128.1
    82]
    14 184 ms 198 ms 178 ms xe-7-0-0.ams10.ip4.tinet.net [89.149.185.89]
    15 185 ms 177 ms 186 ms opendns-gw.ip4.tinet.net [77.67.66.70]
    16 181 ms 201 ms 180 ms resolver1.opendns.com [208.67.222.222]

    Trace complete.
    •  
      CommentAuthordavidu
    • CommentTimeNov 5th 2009
     permalink
    Administrator
    Hopefully tomorrow. It's not clear why this is happening with Sprint since we aren't even announcing that space out of TiNET anymore.
    Thankful People: miked, powerspec88, maintenance
  9.  permalink
    Looks like its fixed this morning!

    Tracing route to resolver1.opendns.com [208.67.222.222]
    over a maximum of 30 hops:

    1 1 ms <1 ms <1 ms 192.168.1.1
    2 81 ms 62 ms 63 ms 68.28.81.69
    3 69 ms 72 ms 65 ms 68.28.81.92
    4 77 ms 67 ms 73 ms 68.28.83.55
    5 * * * Request timed out.
    6 66 ms 74 ms 63 ms 68.28.87.13
    7 * * * Request timed out.
    8 85 ms 82 ms 86 ms 68.28.85.69
    9 97 ms 84 ms 84 ms sl-crs1-kc-0-15-0-0.sprintlink.net [144.223.137.
    225]
    10 91 ms 100 ms 108 ms sl-crs1-chi-0-1-0-3.sprintlink.net [144.232.18.2
    14]
    11 108 ms 74 ms 94 ms sl-st21-chi-13-0-0.sprintlink.net [144.232.20.91
    ]
    12 97 ms 98 ms 105 ms 144.232.18.142
    13 169 ms 131 ms 101 ms 0.so-6-1-0.XL3.CHI13.ALTER.NET [152.63.73.26]
    14 88 ms 82 ms 88 ms POS6-0-0.GW4.CHI13.ALTER.NET [152.63.66.49]
    15 90 ms 78 ms 76 ms 65.199.111.186
    16 85 ms 79 ms 81 ms resolver1.opendns.com [208.67.222.222]

    Trace complete.
    Thankful People: Daniel Gifford
  10.  permalink
    And its back.... Whats wrong this time?

    Tracing route to resolver1.opendns.com [208.67.222.222]
    over a maximum of 30 hops:

    1 1 ms <1 ms <1 ms 192.168.1.1
    2 76 ms 65 ms 76 ms 68.28.81.69
    3 70 ms 122 ms 222 ms 68.28.81.92
    4 87 ms 64 ms 61 ms 68.28.83.54
    5 69 ms 69 ms 61 ms 68.28.87.13
    6 * * * Request timed out.
    7 75 ms 80 ms 89 ms 68.28.85.69
    8 145 ms 80 ms 72 ms sl-crs1-kc-0-15-0-0.sprintlink.net [144.223.137.
    225]
    9 99 ms 123 ms 80 ms sl-crs1-chi-0-5-0-1.sprintlink.net [144.232.18.2
    12]
    10 112 ms 114 ms 107 ms sl-crs1-nyc-0-10-3-0.sprintlink.net [144.232.9.1
    57]
    11 152 ms 148 ms 135 ms sl-gw35-nyc-14-0-0.sprintlink.net [144.232.13.37
    ]
    12 127 ms 545 ms 375 ms sl-tisca1-288260-0.sprintlink.net [144.223.28.23
    0]
    13 301 ms 243 ms 292 ms xe-7-0-0.ams10.ip4.tinet.net [89.149.185.89]
    14 254 ms 188 ms 204 ms opendns-gw.ip4.tinet.net [77.67.66.70]
    15 192 ms 202 ms 229 ms resolver1.opendns.com [208.67.222.222]

    Trace complete.
  11.  permalink
    Administrator
    This should be resolved at this time. Please do a new traceroute to see if the issue still exists.
    Thankful People: Daniel Gifford, maintenance
  12.  permalink
    Looks like its fixed agian!

    Tracing route to resolver1.opendns.com [208.67.222.222]
    over a maximum of 30 hops:

    1 2 ms <1 ms <1 ms 192.168.1.1
    2 77 ms 67 ms 71 ms 68.28.81.69
    3 86 ms 68 ms 67 ms 68.28.81.92
    4 74 ms 64 ms 64 ms 68.28.83.54
    5 78 ms 69 ms 215 ms 68.28.87.13
    6 * * * Request timed out.
    7 70 ms 75 ms 67 ms 68.28.85.69
    8 77 ms 68 ms 62 ms sl-crs1-kc-0-15-0-0.sprintlink.net [144.223.137.
    225]
    9 121 ms 79 ms 75 ms sl-crs1-chi-0-5-0-1.sprintlink.net [144.232.18.2
    12]
    10 83 ms 98 ms 231 ms sl-st21-chi-12-0-0.sprintlink.net [144.232.19.14
    2]
    11 90 ms 77 ms 76 ms 144.232.18.142
    12 84 ms 76 ms 115 ms 0.so-6-1-0.XL3.CHI13.ALTER.NET [152.63.73.26]
    13 125 ms 77 ms 96 ms POS6-0-0.GW4.CHI13.ALTER.NET [152.63.66.49]
    14 86 ms 78 ms 76 ms 65.199.111.186
    15 193 ms 84 ms 79 ms resolver1.opendns.com [208.67.222.222]

    Trace complete.
    Thankful People: Daniel Gifford, maintenance
  13.  permalink
    Tracing route to resolver1.opendns.com [208.67.222.222]

    over a maximum of 30 hops:



    1 <1 ms <1 ms <1 ms 192.168.5.1

    2 1 ms 1 ms <1 ms 192.168.1.1

    3 22 ms 22 ms 148 ms 124.108.52.1

    4 22 ms 22 ms 22 ms 124.108.48.19

    5 24 ms 25 ms 22 ms 203.223.36.13

    6 151 ms 102 ms 84 ms d1-25-230-143-118-on-nets.com [118.143.230.25]

    7 107 ms 106 ms 76 ms 218.189.5.39

    8 233 ms 240 ms 341 ms 203.131.243.109

    9 319 ms 272 ms 404 ms ae-6.r21.newthk01.hk.bb.gin.ntt.net [203.131.240.126]

    10 466 ms 595 ms 404 ms xe-0-1-0.r21.newthk02.hk.bb.gin.ntt.net [129.250.3.61]

    11 866 ms 422 ms 463 ms as-3.r21.tokyjp01.jp.bb.gin.ntt.net [129.250.4.114]

    12 339 ms 302 ms 372 ms ae-3.r21.osakjp01.jp.bb.gin.ntt.net [129.250.4.214]

    13 529 ms 427 ms 251 ms as-1.r21.sttlwa01.us.bb.gin.ntt.net [129.250.3.87]

    14 243 ms 293 ms 318 ms po-3.r00.sttlwa01.us.bb.gin.ntt.net [129.250.4.178]

    15 465 ms 283 ms 291 ms ge-0.opendns.sttlwa01.us.bb.gin.ntt.net [129.250.12.78]

    16 305 ms 328 ms 268 ms resolver1.opendns.com [208.67.222.222]



    Trace complete.
    • CommentAuthorrotblitz
    • CommentTime1 day ago
     permalink
    You're located in Cambodia. What OpenDNS location would you like to use?
  15.  permalink
    i would like to use "Palo Alto, CA".
    • CommentAuthorrotblitz
    • CommentTime18 hours ago
     permalink
    Yeah, I'm located in Germany and would like to use Amsterdam, but I'm routed to London...
    • CommentAuthormarkwew
    • CommentTime8 hours ago
     permalink
    hi good day! Dit is Anne van Frankrijk. wil gewoon frinds hier hebben. en te voldoen aan een speciaal iemand.[url=http://www.netex.com.au/services/search-engine-optimisat]sydney seo[/url]

1 to 17 of 17

  1.