Hank,

Could it be that your HTTP traffic is being passed through a web proxy
that has the correct DNS entry cached?

- Alex


[EMAIL PROTECTED] wrote:


Hello,

I have a GBit Ethernet OSA port (qeth0) dedicated to an zLinux server
(SLES7) under zVM.  The IP address configured for this device is
"172.16.111.101".

ifconfig output
--------------------
wcs-mf-winxs-test:/etc # ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:02:55:9A:EC:9E
         inet addr:172.16.111.101  Bcast:172.16.111.255
Mask:255.255.255.0
         inet6 addr: fe80::202:55ff:fe9a:ec9e/10 Scope:Link
         UP BROADCAST RUNNING NOARP MULTICAST  MTU:1492  Metric:1
         RX packets:7943862 errors:0 dropped:0 overruns:0 frame:0
         TX packets:7837580 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:2873968609 (2740.8 Mb)  TX bytes:3883613591 (3703.7
Mb)


When we had a DNS entry added to our name servers for this device for a WAS application, it was mistakenly added with IP address "172.16.111.103" (.103 instead of .101)

nslookup output
-----------------------
wcs-mf-winxs-test:~ # nslookup testxs.moorewallace.com
Server:  wtc-wins2.moorewallace.int
Address:  10.17.117.226

Name:    testxs.moorewallace.com
Address:  172.16.111.103


The strange thing about this is HTTP traffic is working! I can get to the application from a browser using:

http://172.16.111.103

or

http://testxs.moorewallace.com

I can ping the .103 address from another Linux server on the same
subnet, but not FTP or TELNET.  I can only FTP or TELNET to the .101
addresss, which is what I would expect.

ping output from system on 172.16.111.102
----------------------------------------------------------------
wcs-mf-winxs-db2t:/proc/net # ping 172.16.111.103
PING 172.16.111.103 (172.16.111.103): 56 data bytes
64 bytes from 172.16.111.103: icmp_seq=0 ttl=127 time=0.655 ms
64 bytes from 172.16.111.103: icmp_seq=1 ttl=127 time=0.655 ms
64 bytes from 172.16.111.103: icmp_seq=2 ttl=127 time=0.659 ms


How is HTTP working to the 172.16.111.103 address when it doesn't appear to be configured on the device?





Thanks in advance,

Hank Calzaretta
Moore Wallace, Inc.









Reply via email to