Topic: How do I set up sub-domains with SME 7rc2

[mackayr]

I've got two servers, 3000 miles away from each other (ok ... the distance is irrelevant).  I'd like to set up one server as location2.domain.com, and the other needs to have various sub-domains (www, mail, ftp, forum, location1, etc...) that are accessible both internally (at both locations) and externally.  Therefore, I only have two internet ip addresses.

These are my problems:

1) For the sub-domains that are "built-in" (ie. www, mail and ftp) the only problem I'm having is external users getting an SSL certificate error (ie. the name does not match the certificate - my certificate is attached to www.domain.com, whereas the external users are typing mail.domain.com, ftp.domain.com, etc...).

2) For the other sub-domains on the location 1 server (forum, location1, etc...), I cannot access them internally.  SME attempts to resolve locally, but is unsuccessful since forum.domain.com and location1.domain.com are not recognized).  External users are simply directed to the respective port at my internet ip address.

3) For the location 2 server, external users can access it fine (I've registered the sub-domain to the internet ip address of my location 2 server).  However, internal users at location 1 cannot access it because, once again, the sub-domain (location2.domain.com) is not recognized.  I believe users at location 2 could not access it internally as well, since the sub-domain cannot be resolved locally.

If it's relevant, I'm running 7rc2 at location 1, and 6.5rc1 at location 2.

In summary, I need to avoid having users (internal and external) get SSL errors for the various sub domains (is there a way to set up SME to recognize multiple sub-domains and return the right SSL certificate?) and I need to have internal and external users be able to use all sub-domains (is there a way to configure SME to resolve different sub-domains locally?)  Please help.  I only know enough to be dangerous.

Thanks,

Rob

[jester]

I've got partially similar problems. I have set up IMAPS access to our mail from outside, but users get constant messages in Thunderbird that the supplied certificate does not match the domain: servername.mydomain.com in stead of imap.mydomain.com

Someone knows of a solution?! Maybe self-signed ssl sertificates for the subdomains, but how can this be done?

regards,
jester.

[mackayr]

I've done some further snooping about and it appears that this is indeed a limitation of SME.  What I've done in the interim is set up a sub-domain (registered as a sub-domain that points to my ip address) called "secure.mydomain.com", and I'll use that for any SSL access to my server (ie. secure imap, secure www, etc...).  That works, and avoids the certificate message.

Further, with regard to the sub-domain issue, I've registered the necessary sub-domains externally and pointed them to my ip address (like the "secure" sub-domain), and duplicated this on my hostnames on my server 1.  For the remote one (ie. location2.mydomain.com), I've pointed that to the remote IP.   I never used that feature before, not knowing what it was for ... I guess this is exactly what it's for.  Simple me.  It would have been nicer if my server or my external dns provider would handle it all (both internally and externally), but I suppose my network is small enough that it's not THAT much work to duplicate a few sub-domains.