What about in a cluster? Would it be a good idea to name it:
ny-expc-01.domain.com<http://ny-expc-01.domain.com> ny-expc-02.domain.com<http://ny-expc-02.domain.com> ny-expe-01.domain.com<http://ny-expe-01.domain.com> ny-expe-02.domain.com<http://ny-expe-02.domain.com> What about public/private names? On Sep 4, 2017, at 7:58 AM, Bill Talley <btal...@gmail.com<mailto:btal...@gmail.com>> wrote: Similar to Ryan, I usually try to include "expe" or "expc" as well when the longer name isn't allowed, depending on customers naming standards. Sent from a mobile device with very tiny touchscreen input keys. Please excude my typtos. On Sep 4, 2017, at 7:05 AM, Ryan Huff <ryanh...@outlook.com<mailto:ryanh...@outlook.com>> wrote: I usually keep the names, "edge" and "control" incorporated in them somehow. If I'm trying to save on typing and it's a single pair I might do, "expcontrol" and "expedge". With clusters, I'll add more to the name that denote its purpose or location. Thanks, Ryan On Sep 4, 2017, at 6:17 AM, Matthew Huff <mh...@ox.com<mailto:mh...@ox.com>> wrote: I’m about to deploy our first expressway cluster, what names do people use form expressway DNS names? _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
