ThinClient — Hostname

Scenario

A ThinClient first attempts to obtain a hostname via DHCP. If the DHCP server includes a hostname in the DHCP response (DHCP Option 12), the client adopts it. If the DHCP response lacks a hostname, the client uses the name stored in the openthinclient Manager. If both succeed, the generic hostname openthinclient is used as a fallback. In this case, one of the boot scripts has likely encountered an error. Monitor the boot process again. If necessary, submit a support request in the openthinclient Support Center.

Updating the DNS Server

The system always attempts to communicate the determined name of the thin client to the local DNS server. This is done via a second, subsequent DHCP client request. The response to this request is irrelevant to the client. It's completely discarded and serves solely to transmit the current client hostname back.

Ensure the DNS server accepts dynamic DNS updates via DHCP.

Valid hostnames

Valid characters are: [a-z] [A-Z] [0-9] and -Use only alphanumeric characters and hyphens; start the host name with an alphanumeric character.