Post by Martyn Dale on Apr 6, 2006 4:53:25 GMT -8
There were DNS changes but none that would affect things like that, since like i said before, all other users can still access the server just fine. Also, in traceroutes you provided earlyer, your machine is correctly resolving the IP address. If it was a DNS issue, it would say "cannot find host" or something that. The results however show a destination IP correctly ([67.15.181.14]) which is the role of DNS
It really does sound like a routing problem to me. Once your IP packets contain the destination IP, theres no need to use our DNS again
I could go into the details if the IP protocol but since your not the tech people its not really worth it.
Its possible however an intemediate server between us and them which they use is causing the problems, and therefore why they cant directly fix it, but the traces routes that you provided should identify which server that is.
Making sure you are speakign to someone in networking technical support (or similar dept) will be the best idea, as regular user support techs probably arnt too familiar with exact details of this stuff.
I cant give you a traceroute from this machine, since traceroutes are blocked at my provider, but ill get another 1 from somewhere.
EDIT:
I got one from my parents house.
Tracing route to 6teen.proboards25.com [67.15.181.14]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms BelkinModem.Home [192.168.2.1]
2 191 ms 160 ms 90 ms esr3.ilford5.broadband.bt.net [217.47.23.142]
3 50 ms 70 ms 70 ms 217.47.23.13
4 220 ms 250 ms 251 ms 213.123.78.1
5 20 ms 20 ms 10 ms 217.41.170.66
6 210 ms 230 ms 221 ms 217.41.170.134
7 330 ms 331 ms 340 ms 217.41.170.46
8 201 ms 200 ms 210 ms 213.120.192.170
9 110 ms 110 ms 91 ms core1-pos3-4.ilford.ukcore.bt.net [194.72.20.105
]
10 140 ms 130 ms 151 ms core2-pos7-3.ilford.ukcore.bt.net [194.72.20.2]
11 160 ms 191 ms 180 ms core2-pos13-0.telehouse.ukcore.bt.net [194.74.65
.125]
12 211 ms 220 ms 230 ms g5-2.mpr2.lhr1.uk.above.net [64.125.12.225]
13 250 ms 271 ms 260 ms so-1-1-0.cr2.lhr3.uk.above.net [64.125.27.218]
14 290 ms 311 ms 300 ms so-0-0-0.cr1.lhr3.uk.above.net [208.184.231.145]
15 390 ms 391 ms 411 ms so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]
16 120 ms 100 ms 181 ms so-4-0-0.mpr2.atl6.us.above.net [64.125.28.230]
17 251 ms 250 ms 260 ms so-0-0-0.mpr1.atl6.us.above.net [64.125.27.49]
18 150 ms 121 ms 130 ms so-4-3-0.mpr2.iah1.us.above.net [64.125.31.25]
19 180 ms 201 ms 210 ms t289.216-200-251-162.iah1.us.above.net [216.200.
251.162]
20 240 ms 230 ms 261 ms gphou-66-98-241-29.ev1.net [66.98.241.29]
21 281 ms 290 ms 300 ms gphou-66-98-241-112.ev1.net [66.98.241.112]
22 371 ms 320 ms 361 ms proboards25.com [67.15.181.14]
I cant really see how this will help them, since the traces in that ISP stop before it leaves routers belonging to the ISP, and there are so many routes to Ev1's datacenters, theres no way you will even come close to using the same route as me, until the last couple of steps
I have also PM'ed you an email address for me, if technical support want to speak to me about it give them the address. Continue using this thread for problems though, only use the address for giving to them
It really does sound like a routing problem to me. Once your IP packets contain the destination IP, theres no need to use our DNS again
I could go into the details if the IP protocol but since your not the tech people its not really worth it.
Its possible however an intemediate server between us and them which they use is causing the problems, and therefore why they cant directly fix it, but the traces routes that you provided should identify which server that is.
Making sure you are speakign to someone in networking technical support (or similar dept) will be the best idea, as regular user support techs probably arnt too familiar with exact details of this stuff.
I cant give you a traceroute from this machine, since traceroutes are blocked at my provider, but ill get another 1 from somewhere.
EDIT:
I got one from my parents house.
Tracing route to 6teen.proboards25.com [67.15.181.14]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms BelkinModem.Home [192.168.2.1]
2 191 ms 160 ms 90 ms esr3.ilford5.broadband.bt.net [217.47.23.142]
3 50 ms 70 ms 70 ms 217.47.23.13
4 220 ms 250 ms 251 ms 213.123.78.1
5 20 ms 20 ms 10 ms 217.41.170.66
6 210 ms 230 ms 221 ms 217.41.170.134
7 330 ms 331 ms 340 ms 217.41.170.46
8 201 ms 200 ms 210 ms 213.120.192.170
9 110 ms 110 ms 91 ms core1-pos3-4.ilford.ukcore.bt.net [194.72.20.105
]
10 140 ms 130 ms 151 ms core2-pos7-3.ilford.ukcore.bt.net [194.72.20.2]
11 160 ms 191 ms 180 ms core2-pos13-0.telehouse.ukcore.bt.net [194.74.65
.125]
12 211 ms 220 ms 230 ms g5-2.mpr2.lhr1.uk.above.net [64.125.12.225]
13 250 ms 271 ms 260 ms so-1-1-0.cr2.lhr3.uk.above.net [64.125.27.218]
14 290 ms 311 ms 300 ms so-0-0-0.cr1.lhr3.uk.above.net [208.184.231.145]
15 390 ms 391 ms 411 ms so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]
16 120 ms 100 ms 181 ms so-4-0-0.mpr2.atl6.us.above.net [64.125.28.230]
17 251 ms 250 ms 260 ms so-0-0-0.mpr1.atl6.us.above.net [64.125.27.49]
18 150 ms 121 ms 130 ms so-4-3-0.mpr2.iah1.us.above.net [64.125.31.25]
19 180 ms 201 ms 210 ms t289.216-200-251-162.iah1.us.above.net [216.200.
251.162]
20 240 ms 230 ms 261 ms gphou-66-98-241-29.ev1.net [66.98.241.29]
21 281 ms 290 ms 300 ms gphou-66-98-241-112.ev1.net [66.98.241.112]
22 371 ms 320 ms 361 ms proboards25.com [67.15.181.14]
I cant really see how this will help them, since the traces in that ISP stop before it leaves routers belonging to the ISP, and there are so many routes to Ev1's datacenters, theres no way you will even come close to using the same route as me, until the last couple of steps
I have also PM'ed you an email address for me, if technical support want to speak to me about it give them the address. Continue using this thread for problems though, only use the address for giving to them