|
As far as the pressure WHY to use DIG it may have to do with the "background" on nslookup available at http://en.wikipedia.org/wiki/Nslookup I wonder if these same reasons is why DIG sometimes fails? I tried a few derivations of QSH CMD('nslookup 208.87.182.65 > /nslookupoutput') but I kept getting stuff like ....+....1....+....2....+....3....+....4....+....5.. ************Beginning of data************** ;; connection timed out; no servers could be reached ************End of Data******************** Probably me instead of some difference in how qsHell nslookup works versus IBM i nslookup. Me, I'm more of an API guy. But I'd also check those out on a bunch of different locations. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.