Today, Peter Cavender gleaned this insight:
> > On Wed, 7 Mar 2001, Paul Lussier wrote:
> > > In debugging DNS issues, I'd like to know what servers my DNS lookups are
> > > hitting to make sure things are set up correctly.
> >
> > Briefly: No. The way DNS works does not lend itself to such things.
>
> Briefly, Yes. You just need to install a local DNS cache, such as
> dnscache, part of the djbdns package (http://cr.yp.to/djbdns.html). By
> installing a local cache/resolver, you can 1) get improved performance
But named already does this. If you run a local nameserver, you already
get this by default. Even if you use someone else's name server, you
still get this, by default.
> 2) examine the log files to see the series of recursive queries necessary
> to resolve your lookup. DJB also has several tools that let you see the
> sequence of events in a resolution.
But does it tell you which server DID answer (i.e. provide the ultimate
answer), or which servers MIGHT answer? Both nslookup and dig seem to do
the latter, regardless of what options you give them. Neither is
especially helpful for testing the scenario mentioned by Paul, as far as I
can tell.
But, now that you mention it (and to answer Paul's question more
directly), I think you should be able to get this same information from
your local named by running it with debugging on... So no, you don't need
to install DJB.
As for whether or not named is better or worse than your beloved DJB, I
have no idea, and I don't really care. At the present moment, I simply
don't have time to investigate, given that named is doing it's job, and I
have a giant plate full of other crap that I NEED to do...
So please don't reply saying that DJB is better, because I don't care.
--
Somebody set up us the bomb!
Take off every zig for great justice!
-------------------------------------
Derek Martin
[EMAIL PROTECTED]
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
