× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello Rob,

Am 26.05.2022 um 15:31 schrieb Rob Berendt <rob@xxxxxxxxx>:

It just makes me giddy that the new DNS_LOOKUP table function does not require that you have the following loaded on to your system:
Licensed Product
Program Option Description
5770SS1 31 Domain Name System

Why a client command required a server product baffled me but this gets around it.

Easy: The server isn't required to run on the same system then the client.

Once you configure a DNS server in the TCP/IP settings, the "DNS client" embedded in the TCP/IP can use this one.

Each and every DNS resolution service is using the respective OS APIs under the hood. This is also true for SQL using that API (most likely UNIX-like APIs gethostbyname, gethostbyaddr).

My "idea" to unbundle the command NSLOOKUP was declined but my idea to have a SQL Service to replace NSLOOKUP, and not have a requirement for option 31, was accepted and provided. Yay! Love that DB2 team!

Nice!

:wq! PoC




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 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.