In other words, if your goal is to identify latency in your resolver, it's probably best to run tcpdump on the resolver itself, and analyze the traffic capture to see if there are any latency. The +trace shows you what "should" happen.
On Wed, Nov 7, 2012 at 3:05 PM, david <[email protected]> wrote: > > The +trace option ignores the resolver that you specify after the "@" sign, > and begins at the root. > > > -DTK > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Martin McCormick > Sent: Wednesday, November 07, 2012 1:13 PM > To: [email protected] > Subject: Should Root Servers Always be Queried First? bind9.7.7 > > If I do: > > dig @localhost +short +trace somehost.okstate.edu > > on a server authoritative for the okstate.edu domain, I would expect > resolution via that authoritative system. I do get it but the query takes > the scenic route and I get all the root name servers just as if the query > was for some host outside our domains. > > > Why? We are having issues with random latency right now so I > started > checking everything I could and that is how I discovered this. I don't know > if that is normal or not _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe from this list > > bind-users mailing list > [email protected] > https://lists.isc.org/mailman/listinfo/bind-users > > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe from this list > > bind-users mailing list > [email protected] > https://lists.isc.org/mailman/listinfo/bind-users >
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/bind-users
