<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: distinct hostname per nic on same server in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/distinct-hostname-per-nic-on-same-server/m-p/3775922#M83791</link>
    <description>If you want the hostnames to be available only on that system, you can go with /etc/hosts, as was already suggested.&lt;BR /&gt;However if you want those hostnames to be available in you LAN, you will need to edit the DNS entries. Assuming you are using bind, you will need to edit the zone file that corresponds to your internal domain and add something similar to:&lt;BR /&gt;&lt;BR /&gt;hostname1.     A       132.183.220.x&lt;BR /&gt;hostname2.     A       192.168.0.x&lt;BR /&gt;&lt;BR /&gt;Do not forget to increase the serial number of the zone before reloading it.&lt;BR /&gt;</description>
    <pubDate>Fri, 21 Apr 2006 21:21:16 GMT</pubDate>
    <dc:creator>Manuel Wolfshant</dc:creator>
    <dc:date>2006-04-21T21:21:16Z</dc:date>
    <item>
      <title>distinct hostname per nic on same server</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinct-hostname-per-nic-on-same-server/m-p/3775918#M83787</link>
      <description>Hi there --&lt;BR /&gt;&lt;BR /&gt;I am running SuSE 9.3 on a system that has two NIC's. The eth0 NIC is on one subnet, 132.183.220.x, and eth1 is on a completely separate subnet which in its case is 192.168.0.x. There is no IP-fowarding enabled. &lt;BR /&gt;&lt;BR /&gt;What I am trying to accomplish is to have a hostname associated with the address that eth0 has on its subnet and a completely different hostname for the address that eth1 is using on its subnet. How can I accomplish this? Thanks.</description>
      <pubDate>Fri, 21 Apr 2006 16:10:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinct-hostname-per-nic-on-same-server/m-p/3775918#M83787</guid>
      <dc:creator>Andrew Kaplan</dc:creator>
      <dc:date>2006-04-21T16:10:41Z</dc:date>
    </item>
    <item>
      <title>Re: distinct hostname per nic on same server</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinct-hostname-per-nic-on-same-server/m-p/3775919#M83788</link>
      <description>You can alias in /etc/hosts :&lt;BR /&gt;132.183.220.x &lt;HOSTNAME-OF-SERVER&gt;&lt;BR /&gt;192.168.0.x  &lt;OTHER-NAME&gt; &lt;BR /&gt;&lt;BR /&gt;but what is your purpose? &lt;BR /&gt;&lt;/OTHER-NAME&gt;&lt;/HOSTNAME-OF-SERVER&gt;</description>
      <pubDate>Fri, 21 Apr 2006 16:20:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinct-hostname-per-nic-on-same-server/m-p/3775919#M83788</guid>
      <dc:creator>Antonio Cardoso_1</dc:creator>
      <dc:date>2006-04-21T16:20:57Z</dc:date>
    </item>
    <item>
      <title>Re: distinct hostname per nic on same server</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinct-hostname-per-nic-on-same-server/m-p/3775920#M83789</link>
      <description>Hosts files, as above, and DNS.  That is their purpose.&lt;BR /&gt;&lt;BR /&gt;A physical system can only have one 'hostname', but it can have multiple IP addresses with different DNS names.</description>
      <pubDate>Fri, 21 Apr 2006 16:33:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinct-hostname-per-nic-on-same-server/m-p/3775920#M83789</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2006-04-21T16:33:29Z</dc:date>
    </item>
    <item>
      <title>Re: distinct hostname per nic on same server</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinct-hostname-per-nic-on-same-server/m-p/3775921#M83790</link>
      <description>A different hostname for each ip address is a must. Using /etc/hosts, configure as described above.&lt;BR /&gt;&lt;BR /&gt;The /etc/sysconfig/network should also contain a host name that is related to one of the interfaces.</description>
      <pubDate>Fri, 21 Apr 2006 18:56:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinct-hostname-per-nic-on-same-server/m-p/3775921#M83790</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-04-21T18:56:16Z</dc:date>
    </item>
    <item>
      <title>Re: distinct hostname per nic on same server</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinct-hostname-per-nic-on-same-server/m-p/3775922#M83791</link>
      <description>If you want the hostnames to be available only on that system, you can go with /etc/hosts, as was already suggested.&lt;BR /&gt;However if you want those hostnames to be available in you LAN, you will need to edit the DNS entries. Assuming you are using bind, you will need to edit the zone file that corresponds to your internal domain and add something similar to:&lt;BR /&gt;&lt;BR /&gt;hostname1.     A       132.183.220.x&lt;BR /&gt;hostname2.     A       192.168.0.x&lt;BR /&gt;&lt;BR /&gt;Do not forget to increase the serial number of the zone before reloading it.&lt;BR /&gt;</description>
      <pubDate>Fri, 21 Apr 2006 21:21:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinct-hostname-per-nic-on-same-server/m-p/3775922#M83791</guid>
      <dc:creator>Manuel Wolfshant</dc:creator>
      <dc:date>2006-04-21T21:21:16Z</dc:date>
    </item>
  </channel>
</rss>

