If you're referring to your local system's cache, you can bypass this by specifying a DNS server for dig to query. use @dns.server.domain or @4.2.2.2(for example) for this.
If you're referring to the cache on the server you're trying to query, sorry, that's beyond your control, unless you have root on that server. -wes On Fri, Jan 2, 2009 at 12:11 PM, Stephen Ward < stephen.usenet.w...@wibblywobblyteapot.co.uk> 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
