Re: dig

Re: dig

[Richard Nairn]

Hello,

The two commands are substantially different. Traceroute will give you a
list of machines between you and the specified host. This is the path that
your packets will take.

Dig +trace host.name shows you the discovery route of a host name. It will
show you what the results are from the hierarchy of DNS. For instance it
will show you te list of root servers, primary domain(com, ca, mx), and so
forth until it reaches a machine that can give you the answer for the host
name that you specify.

Hope this helps,
Richard


On Thu, Mar 06, 2003 at 10:52:43AM -0600, David Eduardo Gómez Noguera wrote:
> Hello.
> I haven got the dig output.
> Can anyone help me interpret it?
> 
> It gives a lot of information, but I dont know IP backward and forward,
> so much of its output is obscure to me.
> 
> I tried to find the route up to a host, but i get lost in its output
> (is `dig my.host -trace` somehow equivalent to a traceroute?)
> 
> Thank you for any insight you could give me.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
---end quoted text---

-- 
|       Richard Nairn          Specializing in Linux
|     Nairn Consulting         Web / Database Solutions
|        Calgary, AB           
| Richard@NairnConsulting.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

dig

[David Eduardo Gómez Noguera]

Hello.
I haven got the dig output.
Can anyone help me interpret it?

It gives a lot of information, but I dont know IP backward and forward,
so much of its output is obscure to me.

I tried to find the route up to a host, but i get lost in its output
(is `dig my.host -trace` somehow equivalent to a traceroute?)

Thank you for any insight you could give me.