Perform the following steps to change the DNS and IP address on a single Primary Server zone:
In ZCC, add the additional DNS name (for example, test.epm.blr.novell.com) for the Primary Server, by selecting the Primary Server object and navigating to Settings → Infrastructure Management → Additional DNS Names.
Execute the zman location-response-recompute -f (zman lrr -f) command to re-compute the location configuration response so that the requesting devices can obtain the latest changes.
Ensure that all the devices in the zone are refreshed so that these devices can obtain the newly added DNS in their Closest Server Rules (CSR).
Verify that the CSR on the ZENworks agents is updated with the new hostname.
Test the communication between the Primary Server and the managed devices and ensure that they are able to communicate with each other.
Change the hostname of the Primary Server to the new hostname that was added in Step 1.
Change the IP address of the Primary Server.
Reboot the Primary Server.
Add an entry in the /etc/hosts file of the new IP of the Primary Server and the old hostname to ensure that SSL works.
Rename the Primary Server object in ZCC.
Execute the zac refresh (zac ref) command on the Primary Server to ensure that the new hostname is reflected in ZCC.
Test the communication between the Primary Server and the ZENworks agent on the Primary Server and ensure that they are able to communicate with each other.
Remint the server certificate. While reminting the server certificate, edit the Common Name from the older hostname name to the newly added hostname name (FQDN). For more information, see Reminting Server Certificates in the ZENworks SSL Management Reference.
After the certificate is activated, ensure that the server certificate does not contain the old hostname.
Remove the entry from the /etc/hosts file that was added in Step 9.
Go to the database and remove the additional DNS entry in the table znetworkaddress by running the following query:
delete from znetworkaddress where device = <Device-Guid> and dns = <additional-DNS added> and ipaddress is null and subnetmask is null and macaddress is null and autodetected = 0
Navigate back to ZCC and ensure that the additional DNS name added in Step 1 is not present for the Primary Server.
Test the communication between the Primary Server and the managed devices and ensure that they are able to communicate with each other.