I've been debugging DNS nslookup failures on my home PC and found that a tracert output showed an unusually long delay for one of the hops.
C:\>tracert 202.27.158.40
Tracing route to dnsc1.xtra.co.nz [202.27.158.40]
over a maximum of 30 hops:
1 9 ms 2 ms 1 ms 10.10.2.1
2 14 ms 13 ms 16 ms 219-89-48-1.dialup.xtra.co.nz [219.89.48.1]
3 1455 ms 1693 ms 1303 ms mdr-fid-dom.akcr10.global-gateway.net.nz [202.50.238.50]
4 * 12 ms 14 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.49]
5 13 ms 13 ms 13 ms v4.aksw7.global-gateway.net.nz [210.55.202.51]
6 13 ms 13 ms * xtra-dom-1.aksw7.global-gateway.net.nz [203.96.120.146]
This is from a ADSL2+ connection using a static IP in Auckland 125.236.215.xxx, broadband Pro connection, so internet connectivity should be quite good and unlikely be the cause of the delay.
Connections to remote locations in Africa don't have such large delays.
Is there some problem with the Xtra DNS routing or is it simply an anomaly with the tracert?
BC
Trusted
