Page 1 of 3 123 LastLast
Results 1 to 10 of 25

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

Hybrid View

  1. #1
    Join Date
    Feb 2007
    Location
    Portland, OR
    Posts
    1,147
    Rep Power
    10

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

    While creating a domain I saw a new field that must have been introduced with 5.0.x that doesn't seem to have a clear meaning (at least to me).
    The new field is "Public service host name"

    I have searched the help documentation, the wiki, and the forums and not found anything relevant. Can somebody explain what this field is supposed to do?

  2. #2
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    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:
    zmprov md domain.com zimbraPublicServiceHostname mail.domain.com
    (As long as 'mail' has a proper DNS entry to point at 'server1' both internally and externally.)

  3. #3
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    & before you ask

    Say you have domainA & domainB:

    If you point users at just one address (say it's mail.domainA.com) you just set:
    zmprov mcf zimbraDefaultDomainName domainA.com
    and users can login with username/pass.

    However, user's in domainB.com on the other hand will have to type the full login username@domainB.com/pass.

    To solve that you can create a virtual host. This becomes the default domain for a user login so web-client users can log in without having to specify the domain name as part of their user name.

    Admin console GUI > Domains > Virtual Hosts tab. The virtual host requires a valid DNS configuration with an A record.
    OR
    zmprov md domainB.com zimbraVirtualHostname webmail.domainB.com
    Users enter the virtual host name as the URL address (webmail.domainB.com) where they enter just their username/pass.
    The authentication request searches for a domain with that virtual host name and authentication is completed against that domain.

    Now, if you have a multi server setup you can deploy a login load balancer for the Zimbra server so that all users can log in using the same address/name instead of having to remember which server their mailbox is on.

    You set up a virtual hostname of mail.example.com and configure four mail servers, mail1.example.com to mail4.example.com.

    When users log on to mail.example.com, the load balancer directs the user to any one of the mail servers to verify the log on information. After successfully logging on, users are redirected to the actual server their mail is stored on. While they are logged on, all subsequent requests go directly to their server.

    In order to configure this you must turn on the following for each mail server:
    zmlocalconfig -e zimbra_auth_always_send_refer=true
    We also have an upcoming Bug 9469 - ZCS Mailbox Server Proxy (think of the IMAP/POP proxy principle) to take care of http, soap, rest, caldav, Zimbra Mobile, ZCO, etc.
    -You should see most of that mailbox proxy completed in 5.0.3 as an alpha, except for a few things that we'll announce when it's released.
    Last edited by mmorse; 08-18-2008 at 05:09 PM.

  4. #4
    Join Date
    Feb 2007
    Location
    Portland, OR
    Posts
    1,147
    Rep Power
    10

    Default

    Ok thanks for the info. We have been using virtual hosts for a while now to allow users to login as email.domainname.com (we have ~20 domains running on this server).

    For a while there I was sure that it was generating the share links using the virtual host address but either I was imagining that or it changed recently. I will now put in the address it should show up as in the public service host name field.

    Thanks!

  5. #5
    Join Date
    Feb 2007
    Location
    Portland, OR
    Posts
    1,147
    Rep Power
    10

    Default

    As mmorse stated previously:
    Quote Originally Posted by mmorse View Post
    The server uses zimbraPublicServiceHostname to generate REST URLs, ie: briefcase, document, calendar sharing etc.
    Code:
    zmprov md domain.com zimbraPublicServiceHostname mail.domain.com
    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.)
    So you will need to login to the zimbra user and run
    Code:
    zmprov md defaultdomain.com zimbraPublicServiceHostname ssl.webmaildomain.com
    Edit: And yes it looks like you will have to set it up for every domain.

  6. #6
    Join Date
    Apr 2008
    Location
    Toronto
    Posts
    16
    Rep Power
    7

    Default

    Quote Originally Posted by mmorse View Post
    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.)
    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?

  7. #7
    Join Date
    May 2008
    Posts
    432
    Rep Power
    7

    Exclamation

    A user in the standard default domain defauldomain.com logs in via ssl.webmaildomain.com (our standard webmail login) and views his documents.

    When he clicks on a document, the link generated is : https://mail.defaultdomain.com... instead of https://ssl.webmaildomain.com/...

    How can we change that to always be the correct https://ssl.webmaildomain.com ?

    Thanks

  8. #8
    Join Date
    Feb 2007
    Location
    Portland, OR
    Posts
    1,147
    Rep Power
    10

    Default

    Do you have your public service hostname set to ssl.webmaildomain.com?
    That is what is used to generate the links.

  9. #9
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    Just another note: In 5.0.9+ REST URL's are now composed of 3 attributes: zimbraPublicService[Protocol + Hostname + Port] to avoid dependency on zimbraServer objects. 'Protocal' & 'Port' are automatically configured on upgrade if you have 'Hostname' set. Bug 29978 - remove requirement that zimbraPublicServiceHostname have a corresponding zimbraServer object

  10. #10
    Join Date
    May 2008
    Posts
    432
    Rep Power
    7

    Default

    OK, but how exactly do I set those parameters?

    And do I have to set them for every domain? All users (although they have mail addresses in different domains) log in via one webmail domain.

    Thanks

    Chris
    Last edited by iway; 08-28-2008 at 03:13 PM.

Similar Threads

  1. Replies: 7
    Last Post: 04-27-2009, 03:49 AM
  2. zmclamdctl is not running after upgrade
    By Darren in forum Installation
    Replies: 24
    Last Post: 10-10-2008, 10:10 AM
  3. Suddenly loads of errors in my daily report
    By BarefootPanda in forum Administrators
    Replies: 1
    Last Post: 07-21-2008, 05:09 AM
  4. Replies: 20
    Last Post: 03-18-2008, 06:37 AM
  5. GAL not working with Active Directory
    By ardiederich in forum Installation
    Replies: 13
    Last Post: 02-12-2008, 08:01 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •