...
 
Commits (3)
# nslook-c
simple, concise ip address and hostname lookup, started 1992
simple, concise ip address and hostname lookup, started 1992;
status: complete, fairly stable
nslook
......@@ -17,13 +17,15 @@ was actually necessary to do this dance:
Anyway, I found that extremely tedious, and I also found nslookup's
output too verbose in most situation.
On top of that, in some cases nslookup and its younger sibling
host(1) weren't helpful debugging name lookup problems -- they
always used the resolver library and thus DNS, which wasn't the case
for most other programs, which used gethostbyname(3) and
gethostbyaddr(3). Depending on the system configuration, this
resulted in DNS lookups or not, and for the cases where not, I
needed some other tool to isolate and reproduce an issue.
On top of that, in some cases nslookup and its younger siblings
host(1) and dig(1) weren't helpful debugging name lookup problems --
they always used the resolver library and thus DNS, which wasn't the
case for most other programs, which used gethostbyname(3) and
gethostbyaddr(3). Depending on the system's configuration, this
resulted in DNS lookups or not, and at least for the cases where
not, I needed some other tool to isolate and reproduce an issue
using the standard name lookup whatever it was -- DNS, files, or
NIS, to name a few.
So I wrote nslook(1). The name as a shortened form of "nslookup"
should express what I wanted, a more concise and in some situations
......