Joseph Boyer Jr. wrote:
Jasper,
I would tend to think that the intent of having a host name parameter part of the NIC configuration is to address the needs of multi-homed machines. At least that is what I use them for. In my environment most systems have a public and private interface and I use the hostname associated with each NIC configuration to properly set up /etc/hosts via configuration RPM. I use the system name as the "Node name", that is the name you see when you log into the box or grep HOSTNAME /etc/sysconfig/network.
Correct.
Currently we can serve up a different name via DNS (when cobbler manage_dns is turned on) to each interface in a dual homed system, because it has different IP's.
--Michael
Joseph Boyer Jr Enterprise Technology Services Liquidnet Holdings, Inc. Joseph.Boyer@liquidnet.com T +1 646.660.8352 C +1 646.284.8394
-----Original Message----- From: cobbler-bounces@lists.fedorahosted.org [mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of Jasper Capel Sent: Tuesday, October 14, 2008 4:28 PM To: cobbler mailing list Subject: Static networking -- nameserver configuration and hostnames
Hey all,
Currently, it looks like you can't provide an installed system with a working resolv.conf, if you're not using DHCP (of course you can snippet it). How about a cobbler system edit --name=foo.example.com --name-servers="192.168.0.1 192.168.0.2"?
I also noticed the system's hostname is a property of a network interface. Is this intended, or should we make the hostname a property of the system? I think this is kind of confusing; although anaconda enables you to provide a hostname on each network-line, a system should only have one.
Jasper _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler