B.1 THE DEFINITION OF HOSTNAME
There should not to be a unique or independent hostname for every interface within the system. Literally, there is only one hostname for a system and any other name for a system is known as an alias. Using grandiose host-naming schemes as the alias instead of using it as the official hostname provides the same functionality as when used as an official hostname . Ensure that the forward lookups return all the IP addresses for that system (a feature only available using the DNS) and the reverse address lookups for the IP addresses for that system return the same official hostname as a Fully Qualified Domain Name (FQDN). In addition, ensure that the official hostname and its aliases are entered into name services using only lower case. Following these simple steps will provide you with few "name and address" resolution problems.Many administrators improperly configure hostname naming services (/etc/hosts, NIS, and the DNS) for multi-homed hosts by configuring a separate official hostname for each interface, and then configure the opc_hosts file so that OpenView Operations will resolve the IP address to the proper hostname. This gets them out of the predicament in which they just put themselves by incorrectly configuring hostname naming services! The same scenario applies to authentication and configuration files such as .rhosts, hosts.equiv, inetd.sec, fstab, vfstab, and so on.Configuring the sometimes numerous configuration and authentication files can be quite time consuming, especially when using /etc/hosts or NIS as the primary source of hostname and IP address resolution. When using either of these services as a source of resolution, only one IP will be resolved for a given hostname. This increases labor costs and the costs of owning the products because each alias must be added to authorization files if the service is to be allowed from each interface of an authorized host. |
لطفا منتظر باشید ...
