Routing to opendns
I live in the UK but appear to be using a opendns server based in Frankfurt.
Who do I need to contact to get the routing sorted, opendns or my ISP?
nslookup -type=txt which.opendns.com. 208.67.222.222
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
which.opendns.com text =
"1.fra"
-
Start with opening a support ticket here. OpenDNS may work with their peering network carriers to possibly get it optimized.
Don't forget to include the output of "tracert 208.67.222.222".You can, of course, also contact your ISP if you're confident that their front-line support will even understand what you're taking about at all. ;-)
You may gain funny experiences... -
What a waste of time that was.
Opendns support say it's the ISP's problem.
The ISP say it's Opendns's problem.
Quote OpenDns:
Why are we fast?
Anycast routing, a sophisticated routing technology used by OpenDNS, makes sure you always talk to our nearest datacenter. And in effect, makes Web pages load faster, and your overall Internet experience faster.
I despair :b -
Then, post the output of the following command here:
tracert 208.67.222.222I can probably show you then who/what is the culprit.
Btw, I had the same problem nearly for a year. Although I'm located near Frankfurt, I have been routed to London and Amsterdam, sometimes even to New Yortk..My ISP, three network carriers and OpenDNS were involved in this routing. So pretty clear that there wasn't a quick and easy solution, with five players involved...
I believe it corrected it by itself, because network carriers were changed, I don't recall if it was my ISP or OpenDNS or what. Since then I'm indeed routed to Frankfurt, constantly. Some things heal themselves over time...
-
I suspect level3 need to be contacted to investigate this, but that's not something I can do. Opendns and the ISP show little interest in pursuing the problem, just passing the blame to the other.
To be blunt, I don't think either of the supports understood the problem -- rather disappointing :(
1 5 ms 1 ms <1 ms 192.168.1.254
2 23 ms 29 ms 26 ms lo0-central10.ptw-ag03.plus.net [195.166.xxx.xxx]
3 98 ms 15 ms 18 ms link-b-central10.ptw-gw02.plus.net [212.159.2.154]
4 145 ms 15 ms 14 ms xe-7-2-0.ptw-cr02.plus.net [212.159.1.22]
5 15 ms 18 ms 15 ms ae2.ptw-cr01.plus.net [195.166.129.4]
6 20 ms 15 ms 15 ms te-4-2.car5.London1.Level3.net [217.163.45.249]
7 153 ms 22 ms 24 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]
8 44 ms 23 ms 23 ms ae-59-224.ebr2.London1.Level3.net [4.69.153.141]
9 23 ms 22 ms 25 ms ae-48-48.ebr2.Amsterdam1.Level3.net [4.69.143.81]
10 23 ms 23 ms 22 ms ae-56-221.csw2.Amsterdam1.Level3.net [4.69.153.202]
11 23 ms 22 ms 23 ms 4.69.139.172
12 24 ms 46 ms 23 ms OPEN-DNS-IN.edge6.Amsterdam1.Level3.net [212.72.47.62]
13 23 ms 22 ms 24 ms resolver1.opendns.com [208.67.222.222]
Now routing to Amsterdam, I'll be very interested to hear your opinion on this. -
Yep, you got it! Level-3 is the culprit, they have suboptimal routing configured for those OpenDNS Anycast addresses. It seems OpenDNS is peering in London with network carrier tinet.net. Level-3 seems to attempt to keep the traffic in their own network instead of hand-over to Tinet, therefore routing on to the continent.
Same as with me more than a year ago. And they refused to deal directly with me. They said I must go via my ISP. My ISP raised a ticket with Level-3, but this got lost in the clouds...
Please sign in to leave a comment.
Comments
7 comments