That's funny. I don't have a problem issuing nslookup home.netscape.com on my latest hamm machine.
On the other hand, on an up to date bo machine, I get the same problem you list (the dropping to the nslookup prompt). Upon further investigation, nslookup is a symlink to nslookup.sh which seems to be a wrapper to the host program and not a true binary nslookup. Sorry if I haven't really been following the thread, but could this be part of the problem? Steve Mayer [EMAIL PROTECTED] Jens B. Jorgensen wrote: > > Sure I mean broken because the man page says you can do 'nslookup > home.netscape.com' > but in fact you can't. You have to run 'nslookup' and at the '>' prompt type > your > query. Annoying, isn't it? (It's been this way as long as I can remember but > no, I > haven't logged a bug report.) > > Jay Barbee wrote: > > > > Yeah, the nslookup (or its manpage) is broken. You always have to go into > > > interactive mode. Yuck. Anyway you should try dig, it's fancier. I think > > > it comes in dns-utils. > > > > Hummm, I will try dig, no problem... but could you explain what you mean by > > "broken". Is it some problem with they way I have created the DNS tables? > > Do > > you suggest in uninstall DNSUTILS and reinstall the package? Seems to be > > an environment problem, not a blip in the nslookup binary itself? Just a > > thought. > > -- > Jens B. Jorgensen > [EMAIL PROTECTED] > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
