I've just noticed that when performing traceroutes that the DNS servers don't seem to resolve the host names of the Xnet IP addresses.
Once it leaves the Xnet network it seems to work fine.
They didn't use to look like this, or take as long to complete.
It doesn't seem to be affecting the internet at all, it's just strange.
Tracing route to trademe.co.nz [202.21.128.2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms WRT54GL [192.168.2.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 13 ms 8 ms 10 ms 58.28.15.31
4 13 ms 10 ms 8 ms 58.28.13.83
5 22 ms 20 ms 19 ms 58.28.8.5
6 19 ms 19 ms 19 ms trademe.wix.net.nz [202.7.1.67]
7 19 ms 19 ms 20 ms www.trademe.co.nz [202.21.128.2]
Trace complete.
Tracing route to www.internode.on.net [203.16.214.27]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms WRT54GL [192.168.2.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 13 ms 53 ms 9 ms 58.28.15.31
4 13 ms 10 ms 8 ms 58.28.13.83
5 10 ms 10 ms 9 ms 58.28.8.8
6 13 ms 28 ms 11 ms worldxchange.co.nz [203.110.9.17]
7 11 ms 15 ms 14 ms so-3-0-0.XT1.AKL1.ALTER.NET [210.80.38.133]
8 13 ms 15 ms 14 ms so-2-0-0.BR1.AKL1.ALTER.NET [210.80.38.122]
9 38 ms 40 ms 39 ms atm3-1-0-2.sn1.optus.net.au [202.139.18.17]
10 63 ms 66 ms 63 ms 61.88.221.51
11 62 ms 65 ms 62 ms 61.88.221.51
12 60 ms 66 ms 69 ms internodesystemspl.optus.net.au [59.154.0.18]
13 71 ms 62 ms 59 ms gi1-1.cor3.adl2.internode.on.net [203.16.215.40]
14 57 ms 60 ms 63 ms pubweb.internode.on.net [203.16.214.27]
Trace complete.
Tracing route to trademe.co.nz [202.21.128.2]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms WRT54GL [192.168.2.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 9 ms 10 ms 8 ms 58.28.15.31
4 12 ms 9 ms 9 ms 58.28.13.83
5 19 ms 18 ms 20 ms 58.28.8.5
6 19 ms 19 ms 20 ms trademe.wix.net.nz [202.7.1.67]
7 22 ms 19 ms 20 ms www.trademe.co.nz [202.21.128.2]
Trace complete.
Is anyone else having this issue as well?
Trusted
... 
