<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFCC" text="#000000">
<br>
<br>
On 12/10/11 22:33, Fajar A. Nugraha wrote:
<blockquote
cite="mid:CAG1y0scddnkcaTG58t0M_ttMUDmDz+AbmZ5gskGX-0Ra7Dm7TA@mail.gmail.com"
type="cite">
<pre wrap="">On Thu, Oct 13, 2011 at 3:23 AM, Sten Carlsen <a class="moz-txt-link-rfc2396E" href="mailto:stenc@s-carlsen.dk"><stenc@s-carlsen.dk></a> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Use dig.
Always use dig.
</pre>
</blockquote>
</blockquote>
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">I don't quite agree, for debugging bind, use dig - for debugging lookup
issues on some machine, host will behave more like any normal program, using
resolv.conf and what else and can point to some issues dig will not
discover. E.g. normal SW using something else than DNS, because of some
setup. Dig will never catch this.
</pre>
</blockquote>
<pre wrap="">
If you're concern about what address programs gets when they resolve
host names, then getent is a better choice as it also respects
nsswitch.conf and hosts file.</pre>
</blockquote>
I just tried to make the point that dig is NOT always the perfect
tool, it depends what you want to know. Using dig tells you about
DNS, host and getent and even nslookup tells you more about the
behaviour of your system.<br>
<br>
The right combination of those tools tells you what you need, not
one single tool.<br>
<br>
I was not aware of getent, so thanks for that.<br>
<blockquote
cite="mid:CAG1y0scddnkcaTG58t0M_ttMUDmDz+AbmZ5gskGX-0Ra7Dm7TA@mail.gmail.com"
type="cite">
<pre wrap="">
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>