Re: Is DNS running on their 400?

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>]

how 'bout nslookup <name> <dns> where dns is their machine and name is
something they might have there..

or dig against the dns
or host -a <dns>

got a linux box lying around?  ;-)



===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - AS/400 Administrator
 -- IBM Certified Specialist - RPG IV Developer

"I want to be different, just like everybody else!"
  - Ceili Rain

----- Original Message -----
From: <rob@dekko.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, November 13, 2001 1:27 PM
Subject: Is DNS running on their 400?


>
> Situation:  Remote customer 400 of which we have access.  Stopped sending
> us data and email.  All strictly TCPIP over the Internet.  We can access
> them using telnet, by their name.  However, from their command line we
> cannot ping any outside locations, like nra.org.  Message is unknown host.
> I noticed that their address for their DNS under CFGTCP-12 is the same as
> their interface under CFGTCP-1.  I question as to whether or not they are
> really running DNS on their 400 or if someone's been messing.  They are
> running V4R5.  I am trying to set up to talk to them before I make the
> call.  I can't access their system remotely using Op's Nav.  Is there a
> green screen way of seeing if DNS is configured to run on their 400, like
> perhaps netstat, wrkactjob, or whatever?
>
> Rob Berendt
>
> ==================
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>