Currently, several variants of the sipX host's name (typically, the FQDN, the first component thereof, and the host's IP address) are allowed as aliases of the configured SIP domain name by testing for the host names in parallel with testing for the SIP domain. Unfortunately, this technique doesn't work (which is why we don't use it for implementing domain aliases). It looks like the correct way to handle this is to generate the configuration files as if the allowed host names had been configured as domain aliases. (With the important exception that any host name that is the same as the SIP domain must not be treated as a domain alias -- that would result in an infinite spiral.)