> Not exactly - I am looking to find the actual physical location of the > server. I just ran traceroute and although I am not sure how to > completely interpret the output, it doesn't seem to give me that > information.
You can't do this 100% reliably. A few suggestions: - run whois(1) on the domain name to see who owns it, and where they live. This will be wrong on many occasions because the owner of the domain name may not host the service (think .au domains hosted cheaply in the US). - traceroute to the server and research the hops close to it. If the hostname indicates that there's a router-belrose-001.something the hop ahead of it, you can be pretty sure the machine is in Belrose, for instance. ;-) - See if there's a DNS 'LOC' record for the domain name. This may be wrong or not there at all (they're fairly rare). - Use one of the traceroute clients that attempts to work out the geophysical location of hosts via LOC records, other databases, etc. This won't be wonderfully reliable unless you have Lots Of Money (very expensive services, these ones). Basically, you have a domain name, an ip address, the traceroute output, whois records, and any information on the services available at the site (or even those between you and it). - Jeff -- So, "Jeffrey" seems to mean "the ineffectual, victimised guy in American movies" in four different languages. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
