Logging in changes address to supposed FQDN

[Verbunk]

Hi Guys,

I recently upgraded to the latest Debian Beta and there seems to be a change in the way Zimbra handles the address of the machine.
Basically when I try to login to Zimbra it changes the address to the hostname and domain name I supply the server with. This is ok in my home network but I don't have a pretty (and static) fqdn outside. The behavior used to be it kept the name i signed in with, now something is rewriting the address which breaks things when I'm not inside my network.

Any suggestions?

-J

[KevinH]

Yes we made this change to get the user back on the right machine for a load balanced situation. Can you give more details about the hostnames your trying to use. We thought if we just didn't rewrite the address when it's localhost or an IP address that that'd cover the odd uses but seems there are more. Can you give us some more info on your use case? Thanks.

[Verbunk]

Can you give more details about the hostnames your trying to use. Thanks.

Well, I have DynDNS address ('Q'.homeip.net) I use to initially connect to my firewall (m0n0wall) which I setup to just NAT me over to my debian box on https. The fqdn I setup in my firewall uses domain .maxxnet.net and the hostname it tells the machine to use is mail. I mirrored these settings in the /etc/hosts .

This of course breaks the connection when the address changes to mail.maxxnet.net from the Q.homeip.net I need to connect in.

[Verbunk]

Sorry to pester, any resolution on this? Can this be a switch or something?

[KevinH]

In 3.1 you can add ?redirect=0 to your URL to stop the redirect. The only other solution would be to have a DNS entry for both your internal/external hostname.