hostname not set during autoinstall
Hi, I like to get the hostname passed from DHCP to the client during autoinstall. But whatever I do the hostname is set to "linux". However the IP was set correctly. Platform is IA64 and OS version SLES 10 A snippet from dhcpd.conf: ddns-update-style none; ignore unknown-clients; group { use-host-decl-names on; filename "elilo.efi"; subnet 192.168.72.0 netmask 255.255.255.0 { next-server 192.168.72.72; } host client02 { hardware ethernet 08:00:69:14:04:5E; fixed-address client02; } } ------ and from autoinstall.xml: <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain></domain> <hostname></hostname> </dns> ... ----- Tried several variations with dhcp_hostname/dhcp_resolv also set to false and <hostname></hostname> removed without success. Can't figure out what's wrong... can't even find documentation for dhcp_hostname/dhcp_resolv tags. Any ideas? Hartmut
Hartmut Gottwald <hg@gottwald-home.de> writes:
host client02 { hardware ethernet 08:00:69:14:04:5E; fixed-address client02; }
^^^^^^^^
}
I think you want an IP there, not a hostname. chrs, john. -- "I don't know which is worse, ...that everyone has his price, or that the price is always so low." -Calvin
On 9/11/06 7:22 PM, "John SJ Anderson" <genehack@genehack.org> wrote:
Hartmut Gottwald <hg@gottwald-home.de> writes:
host client02 { hardware ethernet 08:00:69:14:04:5E; fixed-address client02; }
^^^^^^^^
}
I think you want an IP there, not a hostname.
chrs, john.
As long as `nslookup client02` returns an ip address, that format will work. (It does make DHCP dependent on DNS being up and running, which can potentially cause problems -- if the DNS server goes down for longer than the lease time, any machines with dynamic addresses will lose their network connectivity.)
Ian Marlier wrote:
On 9/11/06 7:22 PM, "John SJ Anderson" <genehack@genehack.org> wrote:
Hartmut Gottwald <hg@gottwald-home.de> writes:
host client02 { hardware ethernet 08:00:69:14:04:5E; fixed-address client02; }
^^^^^^^^
}
I think you want an IP there, not a hostname.
chrs, john.
As long as `nslookup client02` returns an ip address, that format will work. (It does make DHCP dependent on DNS being up and running, which can potentially cause problems -- if the DNS server goes down for longer than the lease time, any machines with dynamic addresses will lose their network connectivity.)
The intend is to use a static address on client side. DHCP should only be used during installation to get initial IP and hostname of the node. There is no DNS server, only /etc/hosts is used for the private install network. Thanks, Hartmut
Nobody else with this problem? Hartmut Hartmut Gottwald wrote:
Ian Marlier wrote:
On 9/11/06 7:22 PM, "John SJ Anderson" <genehack@genehack.org> wrote:
Hartmut Gottwald <hg@gottwald-home.de> writes:
host client02 { hardware ethernet 08:00:69:14:04:5E; fixed-address client02; }
^^^^^^^^
}
I think you want an IP there, not a hostname.
chrs, john.
As long as `nslookup client02` returns an ip address, that format will work. (It does make DHCP dependent on DNS being up and running, which can potentially cause problems -- if the DNS server goes down for longer than the lease time, any machines with dynamic addresses will lose their network connectivity.)
The intend is to use a static address on client side. DHCP should only be used during installation to get initial IP and hostname of the node.
There is no DNS server, only /etc/hosts is used for the private install network.
Thanks, Hartmut
John SJ Anderson wrote:
Hartmut Gottwald <hg@gottwald-home.de> writes:
host client02 { hardware ethernet 08:00:69:14:04:5E; fixed-address client02; }
^^^^^^^^
}
I think you want an IP there, not a hostname.
This is the host entry from /etc/hosts and it seems to work as the correct IP is send to client: DHCPACK on 192.168.72.22 to 08:00:69:14:04:5e via eth2 Thanks, Hartmut
chrs, john.
participants (3)
-
Hartmut Gottwald -
Ian Marlier -
John SJ Anderson