Alan,
That was my mistake, I had brought up an old 2.3 system to pull
information from and inadvertently used it's TCP/IP stack (that wasn't
up). (I'm on z/VM 5.4.)
Okay, I've changed NSINTERADDR to point to our internal DNS (actually
DC's).
; NSINTERADDR 127.0.0.1
NSINTERADDR 10.1.2.50
NSINTERADDR 10.1.2.4
I still can't get it to resolve host names. The ping, with a
host/domain name seems to take an inordinate amount of time before
failing:
time ping ibm.com
DTCPIN0014E Unknown host IBM.COM
Elapsed time is 2.01 Minutes.
Ready(00100); T=0.03/0.04 07:53:15
Frank M. Ramaekers Jr.
Systems Programmer MCP, MCP+I, MCSE & RHCE
American Income Life Insurance Co. Phone: (254)761-6649
1200 Wooded Acres Dr. Fax: (254)741-5777
Waco, Texas 76710
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Alan Altmark
Sent: Monday, July 06, 2009 2:03 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Setting up a caching name server.
On Monday, 07/06/2009 at 01:52 EDT, "Frank M. Ramaekers"
<framaek...@ailife.com> wrote:
> I'm attempting to setup a caching name server, but when the VM is
logged
> on, I get a rc of -9 and not much of an explaination:
>
> DTCRUN1021R To cancel Domain Name server startup, type any non-blank
> character
> and press ENTER. To continue startup, just press ENTER.
>
> DTCRUN1011E Server started at 11:26:43 on 6 Jul 2009 (Monday)
> DTCRUN1011E Running "NSMAIN"
> 11:26:46 main: VM TCP/IP Name Server Level 310
> :
> 11:26:49 NsInitPm: Using * as RSCS name
>
> main: error -9 beginning TCP/IP service
> DTCRUN1015I Server ended with RC=-9 at 11:26:49 on 6 Jul 2009 (Monday)
> DTCRUN1019I Server will not be logged off because you are connected
>
> Ideas?
To answer your specific question, error -9 can be found in the TCP/IP
Programmer's Ref. It is in Appendix B, Pascal Return Codes. It means
that VMCF communications failed to the TCPIP stack. The name of the
stack
is coming from TCPIP DATA, so make sure you don't have a bogus TCPIP
DATA
laying around where NAMESRV can see it. [In a later post, you indicated
you fixed the problem, but you didn't say how.]
You appear to be running VM/ESA 2.3 (FL310), a release so old that the
source code has been buried in the back yard in a coffee tin. There
have
been a LOT of fixes since then.
To Frank and others: I recommend that you NOT expend effort to deploy a
name server (caching-only or otherwise) on VM TCP/IP. Given the number
of burned-out light bulbs, broken windows, and rusted pipes, we have
decided to bring in the demoltion crew. NAMESERV is going to slip
silently into that Good Night. Just point NSINTERADDR to the same
nameserver you point everyone else to. With fast servers and networks,
the latency for the DNS lookup won't be an issue.
If your DNS lookup rate is high enough to make an on-board DNS server
worthwhile, then Dr. Boyes' suggestion to run a Linux guest is the way
to
go.
Alan Altmark
z/VM Development
IBM Endicott
_____________________________________________________
This message contains information which is privileged and confidential and is
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any
review, disclosure,
copying, distribution, or use of the contents of this message is strictly
prohibited. If you have
received this in error, please destroy it immediately and notify us at
privacy...@ailife.com.
