Certificate and CNAME records RRS feed

  • Question

  • We have a OCOMM2007 server set up with a certificate, and everything is working fine.
    Is it possible to specify the server name of a CNAME record instead of the hostname in the ocomm client?

    For example, the hostname of the server is SERVER1.domain.com.  I have created a CNAME record called OCOMM.domain.com that points to SERVER1.  Can I get the ocom clients to work by specifying OCOMM.domain.com? Or is this impossible because the name used in the certificate is different than the actual hostname?

    Monday, January 5, 2009 7:17 PM

All replies

  • Its possible, you can use the CNAME for the Certificate.
    Thursday, January 8, 2009 9:50 PM
  • One caveat is that if you are using Automatic Configuration for client look-ups Microsoft states that the SRV record should only point to an A record in DNS, not a CNAME record.  In this case you should simply create a secondary A record for that FQDN that either points to the IP address of Front-End/Director server.  This typically only applies to a Standard Edition server as an Enterprise deployment should already be using a dedicated A record pointing to the pool's virtual IP address.  Also make sure that only the original server1 A record has an associated PTR record, not the secondary A record for ocomm.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Sunday, January 11, 2009 2:14 PM
  • CNAME is not supported in LCS\OCS setup...

    R. Kinker
    MCSE 2003 (Messaging), MCTS - LCS 2005, MCTS - OCS 2007

    Ram Ojha
    Saturday, January 17, 2009 6:50 PM