Once upon a time, Bill Davidsen <davidsen@xxxxxxx> said: > I don't know where the AIX version came from, I'll look to BSD for a solution. > Having used real nslookup on AIX for a decade or so, I'd rather have it just for > me, even if it didn't skip a training/perceptual problem. AFAIK nslookup has always come from BIND (in all the Unix-like OSes, not just Linux), and upstream BIND deprecated nslookup in favor of dig many years ago. IIRC nslookup mucked around in the resolver library's internals (sometimes actually producing wrong results I believe), and when those internals changed, nobody wanted to update nslookup. dig can do everything nslookup could do; you mentioned: - ls - IIRC that did a zone transfer, so is the same as "dig <zone> axfr" - hinfo - that is the same as "dig <host> hinfo" If you need to query a specific nameserver, you add "@<server>". If you don't want the full packet output, you can add "+short" to get just the answer. If you want to set some of these things as defaults, you can put them in $HOME/.digrc (it is read as if it were the start of the command line, so just put the options in there). If your AIX systems are at all current, they should also have dig (if not, complain to IBM that their resolver is ancient, as it is also probably full of bugs); as nslookup has been deprecated by its authors (and AFAIK nobody has stepped up to develop a new and up-to-date version), you are probably going to be better off learning a new tool that is its designated replacement. -- Chris Adams <cmadams@xxxxxxxxxx> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
