Re: Capturing STDERR with -

I suggest you to use Net::DNS. It is not very hard since there is no complex output handling. It has quite simple API and it doesn't require you to do any parsing.

P.S. Another reason to avoid nslookup is that it is deprecated.


bash-2.05a$ nslookup
Note:  nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead.  Run nslookup wit
+h
the `-sil[ent]' option to prevent this message from appearing.
[download]

--
Ilya Martynov (http://martynov.org/)

Comment on Re: Capturing STDERR with - Select or Download Code

Replies are listed 'Best First'.
Re: Re: Capturing STDERR with - by DrManhattan (Chaplain) on Dec 07, 2001 at 19:02 UTC
At a guess, nslookup is probably only "deprecated" on a couple of linux distributions. `$ uname -imprs SunOS 5.8 sun4u sparc SUNW,UltraAX-i2 $ host zsh: command not found: host $ dig zsh: command not found: dig $ nslookup Default Server: bastion.cox.com Address: 206.98.131.2 >` [download] -Matt	[reply] [d/l]
Re: Re: Re: Capturing STDERR with - by blakem (Monsignor) on Dec 08, 2001 at 01:12 UTC
I found a fairly decent faq on nslookups design flaws for anyone interested in that sort of thing. -Blake	[reply]
Re: Re: Re: Capturing STDERR with - by IlyaM (Parson) on Dec 07, 2001 at 19:15 UTC
Actually it have been deprecated by bind maintainers. Some linux distributions do have latest bind but thats all. -- Ilya Martynov (http://martynov.org/)	[reply]