Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Naming and Directory Services (NIS+) |
Part I About Naming and Directory Services
Part II NIS+ Setup and Configuration
4. Configuring NIS+ With Scripts
5. Setting Up the NIS+ Root Domain
Introduction to NIS+ Client Configuration
Security Considerations When Configuring the NIS+ Client
How to Configure an NIS+ Client
Setting Up DNS Forwarding in NIS+
How to Set Up DNS Forwarding in NIS+
Broadcast Initialization in NIS+
Initializing an NIS+ Client by Using the Broadcast Method
How to Initialize an NIS+ Client by Broadcasting
Initializing an NIS+ Client by Using the Host Name Method
How to Initialize an NIS+ Client by Host Name
Initializing an NIS+ Client by Using the Cold-Start Method
How to Initialize an NIS+ Client With a Cold-Start File
NIS+ Client Configuration Summary
8. Configuring an NIS+ Non-Root Domain
10. NIS+ Tables and Information
12. Administering NIS+ Credentials
14. Administering Enhanced NIS+ Security Credentials
15. Administering NIS+ Access Rights
16. Administering NIS+ Passwords
18. Administering NIS+ Directories
20. NIS+ Server Use Customization
23. Information in NIS+ Tables
Common NIS+ Namespace Error Messages
This task changes a machine's domain name. Since a machine's domain name is usually set during installation, you should check it by typing domainname without an argument before you perform this task.
Use the domainname command to change the client machine domain
You must perform this task as superuser on the machine whose domain name you are changing.
Information you need to change a client's domain name:
The machine's superuser password
The new domain name
The examples in this task use client1 as the machine and doc.com. as the new domain name.
client1% su Password:
Type the new name after the domainname command. Do not use a trailing dot. For example, to change a machine's domain to the doc.com domain, you enter:
client1# domainname doc.com
If the machine had been an NIS client, it may no longer be able to get NIS service.
Run the domainname command again, this time without an argument, to display the server's current domain.
client1# domainname doc.com
Redirect the output of the domainname command into the /etc/defaultdomain file.
client1# domainname > /etc/defaultdomain
Even after entering the new domain name into the /etc/defaultdomain file, some processes may still operate with the old domain name. To ensure that all processes are using the new domain name, reboot the machine.
Because you may be performing this task in a sequence of many other tasks, examine the work remaining to be done on the machine before rebooting. Otherwise, you might find yourself rebooting several times instead of just once.
Although restarting individual daemons, such as mountd may solve an NFS problem, it is strongly recommended that you reboot to synchronize configuration changes across daemons. This minimizes application failures caused by unknown changes to the configuration.