Re: nslookup in qsh

Some months ago I tried to use some web service using SYSTOOLS.HTTPGETCLOBVERBOSE and also tried with HTTPAPI service program from SK. Initially HTTPAPI took way longer than the SQL solution with SYSTOOLS. Domain name resolving was the issue. The configuration of the DNS server was not correct. What irritated me then was that the SYSTOOLS method of calling the web service ignored the name solving issue. It seemed that it used some other DNS servers for name resolving. Does this behavior falls in the same category?

Best regards

Mihael


On 26.04.19 09:26, Franz.Rauscher@xxxxxxxxxxx wrote:

yes dig an nslookup have the same behavoir



From: "Bryan Dietz" <bdietz400@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 25.04.2019 20:24
Subject: Re: nslookup in qsh
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



Have you opened a PMR?

Seems like a "miss" from IBM.

"dig" and "host" exhibit the same behavior

Bryan




Franz.Rauscher@xxxxxxxxxxx wrote on 4/25/2019 8:37 AM:

i manually added /etc/resolf.conf with the right parameters and now it
works but i dont think that this is a good solution.

so you have two separate configurations. one for the AS400 Environment

and

one for PASE.

Any opinions?

Greetings,
Franz



From: Franz.Rauscher@xxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxxxxxxxx
Date: 25.04.2019 14:32
Subject: nslookup in qsh
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



hi!

i have a strange problem with nslookup when run in qsh or ssh shell.

i have configured my nameserver with cfgtcp

nslookup, when run from command in a normal 5250 session works fast and

as

expected.

when i run the nslookup command in a qsh shell session i get a timeout
with the message:
;; connection timed out; no servers could be reached

when i add my nameserver to the end of the nslookup like this: nslookup
www.ibm.com 172.25.100.1 than it works
why does nslookup when run in the qsh session not query my nameserver

and

how can i find out which nameserver it tries to query.

Greetings,
Franz


My Data: IBM i 7.3 TR5