adding a DNS Server (IP) and Domain Name to CUCM 9.X

[ccg-collab1]

Hi All,

Good Day. We would like to inquire if what would be the impact if we add a DNS Server (IP) and Domain Name to CUCM 9.X. Currently, there is now DNS configuration for our CUCM 9.X and we are now scheduling of adding a DNS configuration tomorrow. With this, we want to make sure that all action plan will be applied on our activity. Do we need to rehost a license after the adding of DNS?

Found below discussion same on this inquiry:

https://supportforums.cisco.com/discussion/12089806/changing-dns-server-addrresses-cucm-9-cluster

https://supportforums.cisco.com/discussion/11970171/changing-dns-ip-address-cucm-91#4069040

Do we really need to remove the product instances on the PLM (CUCM and CUC)? Then just add them again after the DNS activity?

Thank you so much,

Kier

[Aman Soi]

Hi Kier,

Made the mistake.

you do not need to re-host the licenses.

After u add , domain name , servers would get rebooted on its own.

command are :

set network dns primary

set network domain

regds,

amaan

[ccg-collab1]

Hi Amaan,

Thanks for the response. Do we need to delete the product instances before the adding of DNS? or we can do it after?

Thank you so much,

Kier

[Aman Soi]

[+5] to Jitender.

You need to delete and add new the product instance to avoid license synchronisation failures.

Already mentioned in the link shared by you.

https://supportforums.cisco.com/discussion/11970171/changing-dns-ip-address-cucm-91#4069040

regds,

aman

[Jitender Bhandari]

CCG

For adding DNS

set network dns primary X.X.X.X
set network dns secondary X.X.X.X

To Confirm DNS is there 
show network eth0 – confirm the changes

If you are using ELM you don't need to re-host licenses. To avoid license synchronization failures, delete the product instance from the Enterprise License Manager managing this server's licenses before changing network settings.You will have to re-add the product instance after the network settings have been changed.

Additionally for CUCM highly recommended : restart the Cisco Tomcat service at the CLI with the command utils service restart Cisco Tomcat

JB