[SOLVED] "Public service host name" in domain creation

iway · Post by **iway** » Thu Aug 28, 2008 4:26 pm

I modified the default domain as stated (did that before, actually), but it still generates URLs in the defaultdomain.com way, not the webmaildomain.com.
Any ideas?

iway · Post by **iway** » Thu Aug 28, 2008 4:27 pm

We use redirect mode for https only.

iway · Post by **iway** » Fri Aug 29, 2008 5:12 am

OK, got it working. I set all domains via the Admin interface to the public service hostname.
Thanks
Chris

Ian Forbes · Post by **Ian Forbes** » Tue Oct 14, 2008 10:30 pm

[quote user="mmorse"]The server uses zimbraPublicServiceHostname to generate REST URLs, ie: briefcase, document, calendar sharing etc.
Say it's generating a URL like http:// server1.domain.com and you'd rather have it http:// mail.domain.com:

(As long as 'mail' has a proper DNS entry to point at 'server1' both internally and externally.)[/QUOTE]
Why does mail.domain.com have to resolve internally as well? I ask because my problem is that I have Zimbra installed on an internal domain called server1.corp.domain.com. I have a public DNS name of mail.domain.com that resolves to my Zimbra server. If I set the Public Service Hostname to mail.domain.com then my REST url's are generated as http://mail.domain.com. If a user clicks on that link won't that work?
I don't have an internal zone of domain.com, so I can't resolve server1.domain.com internally. Will this cause me problems?

ArcaneMagus · Post by **ArcaneMagus** » Wed Oct 15, 2008 10:44 am

The only way that will work is if two things are true:

Your mail server is accessible via it's public IP address from your client machines.

The DNS server that the client machines use point mail.domain.com to the Zimbra server's public IP.

In most cases your client machines are on the same subnet/intranetwork as the mail server in which case they will need to have their DNS server point mail.domain.com to the internal IP address of the mail server.
The reason it doesn't just work is because your client machines will have no idea where mail.domain.com points to if you have domain.com on an internal DNS server. If you don't run an internal DNS server then your clients will get the public IP address for mail.domain.com....which will be inaccessible from inside the local network.

Ian Forbes · Post by **Ian Forbes** » Wed Oct 15, 2008 1:42 pm

Thanks for the reply. So, BIND is running on the Zimbra server. The zone configured is for corp.domain.com. The external MX resolves to mail.domain.com (the firewall which forwards to the Zimbra server). My internal users wouldn't know how to resolve mail.domain.com without going out and coming back in. I'm not even sure the firewall wouldn't drop those packets because the source address would be an internal IP.

Obviuosly, split DNS is needed. Would I have to create a new internal zone for domain.com and add a host (A) record for mail.domain.com so my internal users know how to get there?

ArcaneMagus · Post by **ArcaneMagus** » Wed Oct 15, 2008 6:08 pm

Yes that is what you would need to do. Don't forget that things like www. domain.com will also need to be in that internal record as well as any other records you want your internal users to see for domain.com.
Although if you have not had to deal with this issue with your other servers I am guessing that Zimbra is your first internal server as any server, regardless of the type, would have the same issues here of needing internal/external clients to have different IP addresses returned for them...

Ian Forbes · Post by **Ian Forbes** » Wed Oct 15, 2008 6:19 pm

[quote user="ArcaneMagus"]Yes that is what you would need to do. Don't forget that things like www. domain.com will also need to be in that internal record as well as any other records you want your internal users to see for domain.com.
Although if you have not had to deal with this issue with your other servers I am guessing that Zimbra is your first internal server as any server, regardless of the type, would have the same issues here of needing internal/external clients to have different IP addresses returned for them...[/QUOTE]
No. Not at all. I've dealt with infrastructure for a long time. The difference with Zimbra is that they publish these REST features such as shared calendars and documents which external AND internal people need to get to. There are many really good reasons for not having the same internal domain name as your external name. When you do need to do that then split DNS is the way to go...not new to me. I had just installed Zimbra under a different domain name then my outside domain and was wondering how the REST url's would be published and accessed. So, now I know I have to create another DNS zone so my internal users can resolve mail.domain.com. All other servers will continue to live on corp.domain.com.

MACscr · Post by **MACscr** » Wed Jul 21, 2010 11:16 pm

[quote user="iway"]OK, got it working. I set all domains via the Admin interface to the public service hostname.
Thanks
Chris[/QUOTE]
Is there not a per server or global option instead of having to always set this per domain?
Also, i have zmtlsctl mode set to https, yet its still giving out urls to shared contacts for example in http form. Why is that?

dik23 · Post by **dik23** » Wed Jan 26, 2011 7:14 pm

[quote user="MACscr"]Also, i have zmtlsctl mode set to https, yet its still giving out urls to shared contacts for example in http form. Why is that?[/QUOTE]
Same here - did you find out why ?