[cisco-voip] CUCM 6 / set network domain

[Jason Burns]

Changing the domain name will force a restart as soon as the command is
entered.

I would also recommend going through a second cluster reboot after all of
the nodes have been properly set and rebooted once. The second reboot is
necessary to update the /etc/hosts and Informix rhosts files on the first
nodes in the cluster.

For example

Pub
Sub1
Sub2

If you go through and run:

Pub - set network domain / reboot
Sub1 - set network domain / reboot
Sub2 - set network domain / reboot

The Pub will know it has a domain name, but will not know about the new
domain name of Sub1 and Sub2.

Sub1 will know it has a domain name and Pub1 has a domain name, but it will
not know about Sub2.

SUb 2 will know it has a domain name, and know the names of the others.

So after this - do a full cluster reboot one by one starting at the pub.

I think the help for the command tell you this when you run a set network
domain.

Also - make sure your DNS servers are entered on all nodes.



On Mon, Dec 29, 2008 at 2:43 PM, Hughes, Scott GRE/MG
<SHughes at grenergy.com>wrote:

>  Our DNS domain is intra.XXX.com and the short (Windows) domain is XXX. An
> integrator/installer mistakenly set our call managers "domain" to be the
> "short" version causing DNS lookups not to function correctly.
>
>
>
> We have 1 publisher and 1 subscriber.
>
>
>
> Are there any ramifications to changing that with a "set network domain
> intra.XXX.com" on both nodes? Will it require a restart?
>
>
>
> We have CUCM 6.1.1
>
>
>
> Thanks!
>
>
>
> Scott
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081229/8881346b/attachment.html>