Appendix
AX3000 Models 90 - User's Manual 267
A.4.3 - Publishing the Thin Client Name
The thin client name may be registered with the DNS server. This can be done
by the DHCP server or by the thin client itself.
a) By the DHCP Server
Important: the DHCP server must support the DDNS (Dynamic DNS) function.
To register the thin client name by the DHCP server:
- Enable the DHCP protocol
- Set "DNS Server Update" to "by the DHCP server"
Because the DNS server is updated by the DHCP server the information about
the type ("direct" or "direct / reverse") and the result (success or failure) of the
DNS update is not returned to the thin client.
b) By the Thin Client
The thin client can register itself. The thin client behavior depends on the value
of "DNS Server Update" option:
- By the terminal: the thin client updates the DNS server only if the DHCP
server is agreed.
- By the terminal (forced): whatever the DHCP server information, the
thin client updates the DNS server (use carefully).
According to the option 'Update Type', the thin client updates "direct (A)" or
"Direct (A) and Reverse (PRT)" DNS server records.
For a "Direct (A)" update, two entries are added in the DNS server database:
- A "Host" type entry, containing the thin client IP address,
- A "Text" type entry, containing the thin client signature.
Note: the DNS server will be updated only if the thin client name is a full name:
ended by a DNS domain (i.e. FQDN).
For a "Reverse (PRT)" update, one entry is added: a "Pointer" type entry,
containing the thin client’s full name.
To Next Page
Loading...
Need help?
General
