You can dynamically refresh what RESOLVER is using by using this command string, for example:
F resolver,refresh,setup=user55.ressetup EZZ9298I RESOLVERSETUP – USER55.RESSETUP EZZ9298I DEFAULTTCPIPDATA - None EZZ9298I GLOBALTCPIPDATA - SYS1.TCPPARMS(TCPDATA) EZZ9298I DEFAULTIPNODES - USER1.ETC.IPNODES EZZ9298I GLOBALIPNODES - None EZZ9304I COMMONSEARCH EZZ9304I CACHE EZZ9298I CACHESIZE - 200M EZZ9298I MAXTTL - 2147483647 EZZ9298I MAXNEGTTL - 300 EZZ9304I NOCACHEREORDER EZZ9298I UNRESPONSIVETHRESHOLD - 25 EZZ9293I REFRESH COMMAND PROCESSED Regards, Mark Regan, K8MTR General, EN80 CTO1 USNR-Retired (1969-1991), Nationwide Insurance, Retired (1986-2017), z/OS Network Infrastructure Engineering Consultant Checks & Balances, Contractor (2021-2023) Epsilon Inc., Contractor (2023-Present), z/OS Network Systems Programmer On Thu, Jun 5, 2025 at 7:16 AM Mark Pace < [email protected]> wrote: > At this point I'm going to assume that it will take an IPL in order to fix > this. Maybe only cycling TCPIP, But I don't do that, so IPL is going to > have to be the fix. > > On Thu, Jun 5, 2025 at 7:09 AM Mark Pace <[email protected]> wrote: > > > Thank you for that command. It shows exactly what I have previously > posted. > > > > F RESOLVER,DISPLAY > > EZZ9298I RESOLVERSETUP - SYS3.TCPIP.TCPPARMS(RESSETUP) > > EZZ9298I DEFAULTTCPIPDATA - SYS3.TCPIP.TCPPARMS(TCPDATA) > > EZZ9298I GLOBALTCPIPDATA - None > > EZZ9298I DEFAULTIPNODES - None > > EZZ9298I GLOBALIPNODES - None > > EZZ9304I NOCOMMONSEARCH > > EZZ9304I CACHE > > EZZ9298I CACHESIZE - 200M > > EZZ9298I MAXTTL - 2147483647 > > EZZ9298I MAXNEGTTL - 2147483647 > > EZZ9304I NOCACHEREORDER > > EZZ9298I UNRESPONSIVETHRESHOLD - 25 > > EZZ9293I DISPLAY COMMAND PROCESSED > > > > > > On Thu, Jun 5, 2025 at 6:32 AM Mark Regan < > > [email protected]> wrote: > > > >> If you haven't already done so, check your current RESOLVER > configuration > >> by entering the following MVS command string, as shown below: > >> > >> F RESOLVER,,DISPLAY > >> > >> Display > >> > >> Displays the current resolver setup statement values, including the name > >> of > >> the most recently used > >> resolver setup file. If the autonomic quiescing of unresponsive name > >> server > >> function is active, the > >> resolver also displays the status of the name servers specified on > >> NSINTERADDR statements in the > >> global TCPIP.DATA file. > >> > >> The above is from "z/OS Communications Server: z/OS 3.1 Communications > >> Server: IP System Administrator's Commands". > >> > >> Examples of what you may get back are located in the same manual. > >> > >> Regards, > >> > >> Mark Regan, K8MTR General, EN80 > >> CTO1 USNR-Retired (1969-1991), > >> Nationwide Insurance, Retired (1986-2017), > >> z/OS Network Infrastructure Engineering Consultant > >> Checks & Balances, Contractor w/Nationwide Ins. (2021-2023) > >> Epsilon Inc., Contractor (2023-Present), > >> z/OS Network Systems Programmer > >> > >> > >> > >> On Wed, Jun 4, 2025 at 4:45 PM Phil Smith III <[email protected]> wrote: > >> > >> > Well that's interesting. Here's what I see (but I'm not having a > >> problem); > >> > note several "DNS address" entries: > >> > > >> > netstat -qSUM DNS > >> > MVS TCP/IP NETSTAT CS 3.1 TCPIP Name: TCPIP 15:48:25 > >> > Storage Usage: > >> > Maximum: 200M > >> > Current: 25K MaxUsed: 35K > >> > Cache Usage: > >> > Total number of entries: 0 > >> > Non-NX entries: 0 > >> > A: 0 AAAA: 0 PTR: 0 > >> > NX entries: 0 > >> > A: 0 AAAA: 0 PTR: 0 > >> > Queries: 497 Hits: 346 > >> > SuccessRatio: 70% > >> > > >> > DNS address: 9.0.0.1 > >> > Total number of entries: 0 > >> > Non-NX entries: 0 > >> > A: 0 AAAA: 0 PTR: 0 > >> > NX entries: 0 > >> > A: 0 AAAA: 0 PTR: 0 > >> > References: 151 Hits: 0 > >> > > >> > DNS address: 208.67.222.222 > >> > Total number of entries: 0 > >> > Non-NX entries: 0 > >> > A: 0 AAAA: 0 PTR: 0 > >> > NX entries: 0 > >> > A: 0 AAAA: 0 PTR: 0 > >> > References: 151 Hits: 0 > >> > > >> > DNS address: 8.8.8.8 > >> > Total number of entries: 0 > >> > Non-NX entries: 0 > >> > A: 0 AAAA: 0 PTR: 0 > >> > NX entries: 0 > >> > A: 0 AAAA: 0 PTR: 0 > >> > References: 497 Hits: 346 > >> > > >> > -----Original Message----- > >> > From: IBM Mainframe Discussion List <[email protected]> On > >> Behalf > >> > Of Mark Pace > >> > Sent: Wednesday, June 4, 2025 4:40 PM > >> > To: [email protected] > >> > Subject: Re: Resolver Issue > >> > > >> > Not seeing anything useful there. > >> > > >> > > netstat -qSUM DNS > >> > MVS TCP/IP NETSTAT CS V2R5 TCPIP Name: TCPIP 20:38:18 > >> > Storage Usage: > >> > Maximum: 200M > >> > Current: 8K MaxUsed: 9K > >> > Cache Usage: > >> > Total number of entries: 0 > >> > Non-NX entries: 0 > >> > A: 0 AAAA: 0 PTR: 0 > >> > NX entries: 0 > >> > A: 0 AAAA: 0 PTR: 0 > >> > Queries: 0 Hits: 0 > >> > SuccessRatio: 0% > >> > > > >> > > >> > On Wed, Jun 4, 2025 at 3:42 PM Phil Smith III < > >> > [email protected]> wrote: > >> > > >> > > Looks like: > >> > > netstat -qSUM DNS > >> > > might also have been useful? Too late now, but maybe helpful for the > >> > > next victim? I'm not 100% sure--went trolling to see what might be > >> > > used since no IPCONFIG/IFCONFIG and found that. > >> > > > >> > > -----Original Message----- > >> > > From: IBM Mainframe Discussion List <[email protected]> On > >> > > Behalf Of Mark Pace > >> > > Sent: Wednesday, June 4, 2025 3:32 PM > >> > > To: [email protected] > >> > > Subject: Re: Resolver Issue > >> > > > >> > > About 2 mins later. > >> > > > >> > > EZZ9310I NAME SERVER 10.6.0.10 001 > >> > > TOTAL NUMBER OF QUERIES SENT 21 > >> > > TOTAL NUMBER OF FAILURES 21 > >> > > PERCENTAGE 100% > >> > > > >> > > On Wed, Jun 4, 2025 at 3:21 PM Mark Pace <[email protected]> > >> wrote: > >> > > > >> > > > I'll give it a try and keep an eye out. > >> > > > > >> > > > F RESOLVER,FLUSH,ALL > >> > > > EZZ9305I 0 CACHE ENTRIES DELETED > >> > > > EZZ9293I FLUSH COMMAND PROCESSED > >> > > > > >> > > > On Wed, Jun 4, 2025 at 3:09 PM Steely.Mark < > >> > > > [email protected]> wrote: > >> > > > > >> > > >> Try this: F RESOLVER,FLUSH,ALL > >> > > >> > >> > > >> Thanks > >> > > >> > >> > > >> -----Original Message----- > >> > > >> From: IBM Mainframe Discussion List <[email protected]> > On > >> > > >> Behalf Of Mark Pace > >> > > >> Sent: Wednesday, June 04, 2025 2:06 PM > >> > > >> To: [email protected] > >> > > >> Subject: Re: Resolver Issue > >> > > >> > >> > > >> ! > >> > > >> > >> > > >> CAUTION! EXTERNAL SENDER! STOP, ASSESS, AND VERIFY Do you know > this > >> > > >> person? Were you expecting this email? If not, report it using > the > >> > > >> Report Phishing Button! > >> > > >> > >> > > >> IPCONFIG isn't a command on z/OS, it's a configuration statement. > >> > > >> > >> > > >> The only thing I can be sure of is that it is the RESOLVER > sending > >> > > >> the error messages. > >> > > >> > >> > > >> *STC05615* 00000090 $HASP100 RESOLVER ON STCINRDR > >> > > >> *STC05615* 00000090 EZZ9310I NAME SERVER 10.6.0.10 982 > >> > > >> 982 00000090 TOTAL NUMBER OF QUERIES SENT 21 > >> > > >> 982 00000090 TOTAL NUMBER OF FAILURES 21 > >> > > >> 982 00000090 PERCENTAGE 100% > >> > > >> > >> > > >> > >> > > >> *SYS1.PROCLIB(RESOLVER)* > >> > > >> //RESOLVER PROC PARMS='CTRACE(CTIRES00)' > >> > > >> //EZBREINI EXEC PGM=EZBREINI,REGION=0M,TIME=1440,PARM=&PARMS > >> > > >> //SETUP DD > >> DSN=SYS3.TCPIP.TCPPARMS(RESSETUP),DISP=SHR,FREE=CLOSE > >> > > >> > >> > > >> *SYS3.TCPIP.TCPPARMS(RESSETUP)* > >> > > >> DEFAULTTCPIPDATA('SYS3.TCPIP.TCPPARMS(TCPDATA)') > >> > > >> NOCOMMONSEARCH > >> > > >> CACHE > >> > > >> CACHESIZE(200M) > >> > > >> MAXTTL(2147483647) > >> > > >> UNRESPONSIVETHRESHOLD(25) > >> > > >> > >> > > >> *SYS3.TCPIP.TCPPARMS(TCPDATA)* > >> > > >> LOOKUP LOCAL DNS > >> > > >> NAMESERVER 8.8.8.8 8.8.4.4 > >> > > >> NSPORTADDR 53 > >> > > >> RESOLVEVIA UDP > >> > > >> RESOLVERTIMEOUT 30 > >> > > >> RESOLVERUDPRETRIES 1 > >> > > >> > >> > > >> On Wed, Jun 4, 2025 at 2:24 PM Phil Smith III <[email protected]> > >> > wrote: > >> > > >> > >> > > >> > I don't know but I'd try ipconfig and see what it says? Easter > >> > > >> > Egging for sure... > >> > > >> > > >> > > >> > -----Original Message----- > >> > > >> > From: IBM Mainframe Discussion List <[email protected]> > >> On > >> > > >> > Behalf Of Mark Pace > >> > > >> > Sent: Wednesday, June 4, 2025 1:55 PM > >> > > >> > To: [email protected] > >> > > >> > Subject: Resolver Issue > >> > > >> > > >> > > >> > I used to have a linux under VM system that was a DNS server. > >> > > >> > My z/OS systems used this DNS server. Recently I decided to > >> > > >> > retire that DNS server. > >> > > >> > > >> > > >> > I updated the TCPIP.DATA file, removed the 10.6.0.10 address > and > >> > > >> > added > >> > > >> > 8.8.8.8 and 8.8.4.4. > >> > > >> > SYS3.TCPIP.TCPPARMS(TCPDATA) > >> > > >> > NAMESERVER 8.8.8.8 8.8.4.4 > >> > > >> > > >> > > >> > Stopped the resolver and restarted it. > >> > > >> > And it works > >> > > >> > > >> > > >> > EZB3170I Server: dns.google > >> > > >> > EZB3172I Address: 8.8.8.8 > >> > > >> > > >> > > >> > EZB3110I Non-authoritative answer: > >> > > >> > EZB3170I Name: eccgw.southdata.ibm.com > >> > > >> > EZB3172I Address: 170.225.122.67 EZB3175I Aliases: > >> > > >> > eccgw01.boulder.ibm.com > >> > > >> > > >> > > >> > However - I am still receiving this error message. > >> > > >> > > >> > > >> > EZZ9308E UNRESPONSIVE NAME SERVER DETECTED AT IP ADDRESS > >> > > >> > 10.6.0.10 EZZ9310I NAME SERVER 10.6.0.10 940 > >> > > >> > TOTAL NUMBER OF QUERIES SENT 18 > >> TOTAL > >> > > >> NUMBER > >> > > >> > OF FAILURES 18 PERCENTAGE > >> > > >> > 100% > >> > > >> > > >> > > >> > Why would I still receive this error? > >> > > >> > > >> > > >> > -- > >> > > >> > The postings on this site are my own and don’t necessarily > >> > > >> > represent Mainline’s positions or opinions > >> > > >> > > >> > > >> > Mark D Pace > >> > > >> > Senior Systems Engineer > >> > > >> > Mainline Information Systems > >> > > >> > > >> > > >> > > ----------------------------------------------------------------- > >> > > >> > -- > >> > > >> > --- For IBM-MAIN subscribe / signoff / archive access > >> > > >> > instructions, send email to [email protected] with the > >> > > >> > message: INFO IBM-MAIN > >> > > >> > > >> > > >> > > ----------------------------------------------------------------- > >> > > >> > -- > >> > > >> > --- For IBM-MAIN subscribe / signoff / archive access > >> > > >> > instructions, send email to [email protected] with the > >> > > >> > message: INFO IBM-MAIN > >> > > >> > > >> > > >> > >> > > >> > >> > > >> -- > >> > > >> The postings on this site are my own and don’t necessarily > >> > > >> represent Mainline’s positions or opinions > >> > > >> > >> > > >> Mark D Pace > >> > > >> Senior Systems Engineer > >> > > >> Mainline Information Systems > >> > > >> > >> > > >> > ------------------------------------------------------------------- > >> > > >> -- > >> > > >> - For IBM-MAIN subscribe / signoff / archive access instructions, > >> > > >> send email to [email protected] with the message: INFO > >> > > >> IBM-MAIN > >> > > >> > >> > > >> > ------------------------------------------------------------------- > >> > > >> -- > >> > > >> - For IBM-MAIN subscribe / signoff / archive access instructions, > >> > > >> send email to [email protected] with the message: INFO > >> > > >> IBM-MAIN > >> > > >> > >> > > > > >> > > > > >> > > > -- > >> > > > The postings on this site are my own and don’t necessarily > represent > >> > > > Mainline’s positions or opinions > >> > > > > >> > > > Mark D Pace > >> > > > Senior Systems Engineer > >> > > > Mainline Information Systems > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > >> > > -- > >> > > The postings on this site are my own and don’t necessarily represent > >> > > Mainline’s positions or opinions > >> > > > >> > > Mark D Pace > >> > > Senior Systems Engineer > >> > > Mainline Information Systems > >> > > > >> > > > ---------------------------------------------------------------------- > >> > > For IBM-MAIN subscribe / signoff / archive access instructions, send > >> > > email to [email protected] with the message: INFO IBM-MAIN > >> > > > >> > > > ---------------------------------------------------------------------- > >> > > For IBM-MAIN subscribe / signoff / archive access instructions, send > >> > > email to [email protected] with the message: INFO IBM-MAIN > >> > > > >> > > >> > > >> > -- > >> > The postings on this site are my own and don’t necessarily represent > >> > Mainline’s positions or opinions > >> > > >> > Mark D Pace > >> > Senior Systems Engineer > >> > Mainline Information Systems > >> > > >> > ---------------------------------------------------------------------- > >> > For IBM-MAIN subscribe / signoff / archive access instructions, send > >> email > >> > to [email protected] with the message: INFO IBM-MAIN > >> > > >> > ---------------------------------------------------------------------- > >> > For IBM-MAIN subscribe / signoff / archive access instructions, > >> > send email to [email protected] with the message: INFO > IBM-MAIN > >> > > >> > >> ---------------------------------------------------------------------- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected] with the message: INFO IBM-MAIN > >> > > > > > > -- > > The postings on this site are my own and don’t necessarily represent > > Mainline’s positions or opinions > > > > Mark D Pace > > Senior Systems Engineer > > Mainline Information Systems > > > > > > > > > > -- > The postings on this site are my own and don’t necessarily represent > Mainline’s positions or opinions > > Mark D Pace > Senior Systems Engineer > Mainline Information Systems > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
