When setting a new primary DNS server in the Cisco UCM CLI, what is required for the change to take affect?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/211393-Change-CUCM-Server-Definition- https://community.cisco.com/t5/ip-telephony-and-phones/cucm-10-5-host-name-and-dns-change/td-p/2996878When setting a new primary DNS server in the Cisco Unified Communications Manager (UCM) Command Line Interface (CLI), a restart of the network service is required for the change to take effect.
Here's a more detailed explanation:
Cisco UCM uses DNS servers to resolve hostnames and IP addresses of servers and devices in the network. When configuring a new primary DNS server, it is necessary to update the network settings in UCM to reflect the new DNS server. This is typically done through the UCM Command Line Interface (CLI).
To configure a new primary DNS server in UCM, you can use the "set network dns" command in the CLI. For example:
sqlset network dns primary X.X.X.X where X.X.X.X is the IP address of the new primary DNS server.
After running this command, UCM will update its network settings to use the new primary DNS server. However, this change will not take effect until the network service is restarted. This is because the network service is responsible for handling DNS resolution in UCM.
To restart the network service, you can use the "utils service restart Cisco Network" command in the CLI. For example:
utils service restart Cisco Network
Once the network service is restarted, UCM will begin using the new primary DNS server for hostname and IP address resolution.
To summarize, when setting a new primary DNS server in the Cisco UCM CLI, a restart of the network service is required for the change to take effect.