I'm imagining you want a way to make dig act like the caching
nameserver and do what it would do and show you the answer.
dig +trace does something similar to this. There is no nameserver
operation
that dig could do to tell a caching nameserver to act differently
for one query. You could clear the nameserver's cache, or even
clear the one name you are interested in out of the cache.
Sometimes querying another name in the domain you are interested
in is sufficient for whatever you are checking.
In certain situations, it can be very helpful to check someone else's
caching nameserver, so it is helpful to have a few such addresses
on hand. These days, a lot of sites are closing their caching servers
(go figure!),
and I've been using OpenDNS's servers.
On Jan 2, 2009, at 8:11 PM, Stephen Ward wrote:
For all my attempts to read the manual on DIG I can't find a way to do
something really simple.
Is there a way to dig a domain name so even if the results are in
cache,
it will ignore these and re-read them? It's really from a testing
perspective I'm looking at this. I can mash the keyboard each time to
try
and get a better handle on the query time, but there has got to be an
easy way to do this?
--
. . .
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
