Re: HTTP api quit working on Friday

["Eric Jones" <Eric.Jones@xxxxxxxxxx>]

This was an AT&T problem
the first DNS ip address wasn't working at all
we removed it with the chgtcpdmn command per Scotts advice
the second one is slow but at least it works.
We are in contact with AT&T to resolve.
Thanks again, Eric


>>> "Eric Jones" <Eric.Jones@xxxxxxxxxx> 7/29/2008 4:59 PM >>>
Alright I see 2 ip addresses there, as far as I know everything looks normal there.
I have my "best" "network" guy looking into it, thanks for the help guys.

>>> Scott Klement <sk@xxxxxxxxxxxxxxxx> 7/29/2008 4:30 PM >>>
Prompt the CHGTCPDMN command.

It should have a 'Domain name server' (INTNETADR) parameter that lists 
one or more DNS servers.   When you ask it to convert a domain name to 
an IP address, it will send the lookup requests to the servers in that list.


Eric Jones wrote:
> Nobody is feasing up to anything. I think I have a clue though.
>>From my as400 I can ping 69.128.116.164
> but I can not ping  www.scottklement.com 
> how does the as400 resolve an IP ? where do I find the dns?
> 
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi 
-----------------------------------------------------------------------



-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi 
-----------------------------------------------------------------------



-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------