[Techtalk] traceroute questions

[Rasjid Wilcox]

On Tuesday 17 February 2004 10:08, Emma Jane Hogbin wrote:
> But from my client's computer, the traceroute fails:

A bit of googling turned up this guide to traceroute:
http://www.exit109.com/~jeremy/news/providers/traceroute.html

There are a number of reasons why traceroute may fail, but I don't think any 
of them have anything to do with DNS issues.  Generally routing issues or 
ICMP packets being blocked at some point on the route.

> So where does the problem lie? My ISP is trying to tell me that I have a
> firewall installed on the server. I've done a plain debian install which
> does NOT include a firewall. My ISP is refusing to help because I have
> debian installed. I'm pretty sure it's not actually my fault though....

Traceroute failing does not necessarily mean there is a problem as such.

For example, I can definitely get to (and even ping) www.bigpond.com.au, but:
# traceroute -n www.bigpond.com
traceroute to www.bigpond.com (144.135.18.32), 30 hops max, 40 byte packets
 1  xxx.xxx.xxx.xxx 0.483 ms   0.403 ms   0.463 ms
 2  203.56.186.1  1.243 ms   21.369 ms   35.714 ms
 3  10.192.0.10  22.092 ms   21.541 ms   33.600 ms
 4  203.63.118.194  22.535 ms   27.469 ms   24.563 ms
 5  203.63.113.62  38.591 ms   35.117 ms   44.069 ms
 6  202.10.4.57  32.873 ms   46.027 ms   52.276 ms
 7  202.10.0.37  60.850 ms   59.783 ms   57.548 ms
 8  202.10.4.10  58.506 ms   67.282 ms   95.517 ms
 9  139.130.1.193  76.928 ms   71.567 ms   72.498 ms
10  203.50.12.153  74.053 ms   86.840 ms   74.431 ms
11  203.50.13.2  78.092 ms   91.764 ms   100.109 ms
12  139.130.185.254  105.932 ms   111.974 ms   125.306 ms
13  * * *
14  * * *
15  * * *

Perhaps you could describe what the DNS problem is instead?

Cheers,

Rasjid.

-- 
Rasjid Wilcox
Canberra, Australia (UTC +11 hrs)
http://www.openminddev.net