Lots of systems get really upset if you try to assign multiple hostnames to the same tcpip stack. I set up two different DNS domains for this type of configuration.
Each host on the network has only one hostname: Linux1 Linux2 etc Each host is actually a member of two domains: my.external.net: 192.168.70.0/24 my.hipersocket.net: 10.1.1.0/24 So, Linux1 has only one hostname - Linux1 - but it has two fully qualified hostnames: Linux1.my.external.net Linux1.my.hipersocket.net Both domains (zones?) are defined in the DNS that is out on the 192.168.70network, so you alter the domain part of the FQDN to control which network you use to get to an adjacent system. It seems to work well. -- Jay Brenneman ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
