Lately, I've noticed a strange lookup error in my cluster of machines running x86 SL5. The DNS server for my cluster, honker.physics.winona.edu, comes up "properly" through the host or nslookup command, but when I try to ssh to the node (from another machine) "honker" gets mapped to the localhost IP address. See the following text for an example,
[EMAIL PROTECTED] etc]# host honker honker.physics.winona.edu has address 10.30.27.5 [EMAIL PROTECTED] etc]# nslookup honker Server: 10.30.27.5 Address: 10.30.27.5#53 Name: honker.physics.winona.edu Address: 10.30.27.5 [EMAIL PROTECTED] etc]# ssh honker The authenticity of host 'honker (127.0.0.1)' can't be established. RSA key fingerprint is c9:cb:ee:af:80:d9:76:e1:88:f0:fc:1a:e2:a3:a0:07. Are you sure you want to continue connecting (yes/no)? no Host key verification failed. When I say yes to this ssh command, the command fails in that I ssh to the machine I'm already on (127.0.0.1) rather than to the proper target ( 10.30.27.5). This seems like a problem, but I'm not sure where to look to fix it. While trying to understand this problem I looked in the /etc/hosts file that came standard with SL5. The second line looks quite foreign to me, [EMAIL PROTECTED] ~]# cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 buff localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 Can someone explain what the "localhost6" does? regards, Nathan Moore -- - - - - - - - - - - - - - - - - - - - - - Nathan Moore Assistant Professor, Physics Winona State University AIM: nmoorewsu - - - - - - - - - - - - - - - - - - - - -
