Gareth, Paul, et al,
> dig is the seminal tool for testing all things DNS related. It's simple
> to use, but very powerful.
Just an off-topic footnote: As per Gareth's post, dig is a recommended
tool to check up on the "caching" mechanisms in bind, the DNS timings,
etc. The first access to an external site may take 20-100-500-750
millisecs. If the caching is working well, subsequent accesses should be
under 1 millisec.
BUT - my guess is that dig is observing the timings, WHILE it is
displaying the output data, rather than running all the timings first,
and THEN displaying all the results. However, I've not checked the
- if you're running dig in any standard "console", and
- the output from dig is scrolling on the screen, and
- you're interested in the lookup timings, and
- the DNS lookups are cached (and take only some microsecs), then
practically ALL the timings will relate to the scrolling speed of the
console handlers rather than the DNS lookup speeds!!
So... I suggest something like: clear; dig xxxxxx
Also, AFAIK, if you're using the /etc/hosts file to filter out the crap
sites, dig does not honour its contents.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!