[cisco-voip] can CUCM config w/ FQDN be avoided any more?

[Lelio Fulgenzi]

So, we, like many others, went with IP addresses as hostname in our CUCM cluster. Best practice, avoid DNS issues, etc.

But now, certificate authorities will not grant certificates to private IP addresses and we need (would like) publicly signed certificates to avoid those pesky errors.

I really can't see a way to avoid not using FQDN in CUCM configs any longer.

>From what I recall, the reliance on DNS was on system/service (re)start-up and after that, no real reliance. Not sure if the local tables age out or not.

What are people's thoughts and experiences?


---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
lelio at uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 14993 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170919/288ebec2/attachment.bin>