Re: nslookup

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Richard, Jack,
Yes, if you do not have option 31, dns loaded on your system you do not
have QSYS/NSLOOKUP *CMD.  This was a major reason why I submitted an idea
to create the nslookup sql service which was accepted and completed.  In my
idea I requested, and got, that option 31 would not be required to be on
your system.
And I only just now discovered that there is a STRDNSQRY command, which
also requires option 31.
See also DIG or STRDIGQRY, again, which require option 31.
See also HOST or STRHOSTQRY, again, which require option 31.
Since the documentation on nslookup is saying it is deprecated and you
should use DIG it's unlikely we'll get a native nslookup command which does
not require option 31.
https://www.ibm.com/docs/en/i/7.5?topic=ssw_ibm_i_75/cl/nslookup.html
I like the IBM command naming convention.  That being said however, I am
going to use the multiplatform names.  Like, I would use PING and never use
VFYTCPCNN.  If you do a DSPCMD on both of these you will see they use the
exact same program.



On Fri, May 24, 2024 at 12:38 PM Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
wrote:

> Maybe I interpreted wrong, but I think his question was about whether the
> NSLOOKUP command would be still supported since it appeared to be part of
> option 31, dns server.
>
> Regards,
> Richard Schoen
> Web: http://www.richardschoen.net
> Email: richard@xxxxxxxxxxxxxxxxx
>
>
> ------------------------------
>
> message: 4
> date: Fri, 24 May 2024 16:06:18 +0000
> from: Jack Woehr via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
> subject: Re: nslookup
>
> Not dropping NSLOOKUP ... the DNS server is to make your IBM i  be a DNS
> server which it seems nobody does anymore.
>
> Not having a DNS server does not stop DNS exploratory utilities from
> working. For instance, nslookup just goes to whatever you've configured to
> be the dns server you do lookups against, usually some VM in the data
> center, or 8.8.8.8 for Google.
> ________________________________
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of
> Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
> Sent: Friday, May 24, 2024 9:05 AM
> To: midrange-l@xxxxxxxxxxxxxxxxxx <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: RE: nslookup
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
> Not sure what it means for the NSLOOKUP command, but FWIW there is also a
> PASE version of nslookup available.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.