Quote from: routeflap on November 06, 2008, 05:24:03 AM
My /64 is routed correctly:
I would sugest checking this out.
Both:
$ traceroute6 2001:470:1d:72::1
$ traceroute6 2001:470:1d:72::2
End with
10 2001:470:1c:72::2 (2001:470:1c:72::2) 148.732 ms 151.169 ms 149.133 ms
11 2001:470:1c:72::2 (2001:470:1c:72::2) 150.864 ms !H 149.504 ms !H 163.052 ms !H
So - Host not reachable
And speaking of improving things (HE):
There are few routers without revdns on the traceroute below.
Cheers,
PJ
2 gige-g2-4.core1.fra1.he.net (2001:470:0:69::1) 39.251 ms 38.773 ms 39.144 ms
3 10gigabitethernet1-4.core1.ams1.he.net (2001:470:0:47::1) 49.55 ms 45.724 ms 46.013 ms
4 10gigabitethernet1-4.core1.lon1.he.net (2001:470:0:3f::1) 54.318 ms 54.482 ms 55.382 ms
5 10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1) 123.042 ms 124.14 ms 135.637 ms
6 10gigabitethernet1-2.core1.nyc1.he.net (2001:470:0:37::2) 126.811 ms 124.686 ms 141.08 ms
7 2001:470:0:a8::2 (2001:470:0:a8::2) 128.698 ms 123.879 ms 122.885 ms
8 2001:470:0:ae::2 (2001:470:0:ae::2) 139.558 ms 139.642 ms 140.467 ms
9 2001:470:0:c0::2 (2001:470:0:c0::2) 140.119 ms 147.505 ms 138.857 ms
10 2001:470:1c:72::2 (2001:470:1c:72::2) 327.295 ms 200.582 ms 202.071 ms
11 2001:470:1c:72::2 (2001:470:1c:72::2) 198.181 ms !H 203.937 ms !H 175.41 ms !H
EDIT:
With !H beeing shown on the traceroutes both 2001:470:1c:72::1(2) respond to pings.
I believe Sam addressed this in the trouble ticket you opened.
As for rdns, we'll update accordingly.