Same boat here. DNS however has proven quite reliable and in hindsight, we did not need to fear it.
We are worried that turning on DNS could potentially invalidate the certificates use to verify phones are talking to the right cluster. If we did use DNS, I am sure we would have used FQDN to specify our voice mail servers, out SIP trunks and sundry other services so we would be dependant on it all the time. Do let us know how your change goes. d On Tue, Sep 19, 2017 at 9:33 AM, Lelio Fulgenzi <le...@uoguelph.ca> wrote: > > > 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 <(519)%20824-4120> > > le...@uoguelph.ca > > www.uoguelph.ca/ccs > > Room 037, Animal Science and Nutrition Building > > Guelph, Ontario, N1G 2W1 > > > -- Copyright 2017 Derek Andrew (excluding quotations) +1 306 966 4808 Communication and Network Services Information and Communications Technology Infrastructure Services *University of Saskatchewan*Peterson 120; 54 Innovation Boulevard Saskatoon,Saskatchewan,Canada. S7N 2V3 Timezone GMT-6 Typed but not read.
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
