Hello. I am using autoyast/sles9. I just started building hosts with more than 1 physical ethernet interface which resulted in some surprising entries in the /etc/hosts file. here is the snippet of my control.xml file that pertains to the hosts networking setup. <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dns> <domain>atl.company.com</domain> <hostname>app01</hostname> <nameservers config:type="list"> <nameserver>172.17.9.25</nameserver> </nameservers> <searchlist config:type="list"> <search>atl.company.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <startmode>onboot</startmode> <broadcast>172.17.177.255</broadcast> <netmask>255.255.255.0</netmask> <ipaddr>172.17.177.54</ipaddr> </interface> <interface> <bootproto>static</bootproto> <device>eth1</device> <startmode>onboot</startmode> <broadcast>10.170.3.255</broadcast> <netmask>255.255.255.0</netmask> <ipaddr>10.170.3.21</ipaddr> </interface> </interfaces> The resulting hosts file has these 2 entries. 10.170.3.21 app01.atl.company.com 172.17.177.54 app01.atl.company.com app01 The question is. Why is the line "10.170.3.21 app01.atl.company.com" being added to the /etc/hosts file? If I cannot stop this from occuring can I at least control the name that gets associated with the 2nd interface so I might end up with 10.170.3.21 eth1-app01.atl.company.com or something like that? TIA. Deet.