Alias Issue with OS X Server Messages Service

19 Feb Alias Issue with OS X Server Messages Service

Overview

We have run into an issue with using an hostname alias with the Messages service on OS X Server requiring the configuration to be modified after every OS X Server application update. The ALIAS record maps a name to another name, but in turns it can coexist with other records on that name.

Workaround

On the OS X Server, stop the Messages service with the following command:

sudo serveradmin stop jabber

Enter the administrator password:

Password:

And you should get the following output if the Messages service has properly stopped:

jabber:state = "STOPPED"

Or turn OFF the Messages service using the Server application:

Then open the following sm.xml file with your favorite text editor:

/Library/Server/Messages/Config/jabberd/sm.xml

Edit the following text:

<local>
     <!-- Who we identify ourselves as.
     Users will have this as the domain part of their JID.
     If you want your server to be accessible from other
     Jabber servers, this IDs must be FQDN resolvable by DNSes.
     If not set, the SM id is used. -->
     <id>server.mydomain.edu</id>
     <!--
<id>vhost1.localdomain</id>
<id>vhost2.localdomain</id>
-->
</local>

You want to add your server alias hostname underneath the line for your server primary hostname.

For example:

<local>
     <!-- Who we identify ourselves as.
     Users will have this as the domain part of their JID.
     If you want your server to be accessible from other
     Jabber servers, this IDs must be FQDN resolvable by DNSes.
     If not set, the SM id is used. -->
     <id>server.mydomain.edu</id>
     <id>alias.mydomian.edu</id>
     <!--
<id>vhost1.localdomain</id>
<id>vhost2.localdomain</id>
-->
</local>

On the OS X Server, start the Messages service with the following command:

sudo serveradmin start jabber

Enter the administrator password:

Password:

And you should get the following output if the Messages service has properly started:

jabber:state = "RUNNING"

Or turn ON the Messages service using the Server application:

Next, launch your Messages client software and test the modification is working properly with your server hostname alias.