[SOLVED] Help for ubuntu newbie.

[Narev]

Hi all, first of all i would like to ask you bear with me. I know this question has been asked 1000's of times but still i cannot seem to sole my problem Also the fact that im new to linux does not help me either.

I am trying to install ZCS 6.08 on Ubuntu 8.04.4 LTS with changing results. When i first tried to install it locally it worked but ever since we plugged the server into the dmz environment i have not even been able to reach the webaccess. In our situation we have a local dns server so there is no need to set up the zimbra server as a DNS.

Due to me being completly new to Linux i have a hard time to determine where the problem could lie so ill provide you with my config files i think matter:

/etc/hosts

127.0.0.1 localhost
127.0.0.1 zimbraserver.localdomain.dmz zimbraserver
192.168.200.30 zimbraserver.localdomain.dmz zimbraserver

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

/etc/resolv.conf

search localdomain.dmz
nameserver local.dns.server.ip

Because i installed zimbra earlier befor the dmz i used
su - zimbra
/opt/zimbra/libexec/zmsetservername -n to change the servername to both localdomain.dmz and externaldomain.nl. However, i still am not able to reach my zimbra server. Which one should it be? should the hostname be my forwarded publichostname.publicdomain.nl ? or my hostname.localdomain.dmz??

It should also be noted that my zmcontrol status also tells me that the logger service is not started and that the ldap services states that it cannot find the ldap service and will use a caches version.

I am able to ping my server on both its external domain as on its local domain but i cannot reach the webaccess via http://local-ip and neither by http://exeternaldomain.nl or http://localdomain.dmz

What could this be? I am also pretty sure that the port 80 is forwarded to the server.

One final note is that we have not set our MX record yet, because we already have an MX record set to this domain that we are still using so we still need to configure it correctly but we figured that it might be a good way to test the webaccess and admin portal.

[phoenix]

Your hosts file is incorrect, go to the Split DNS article and look at the format described there for the hosts file and make yours the same. You should also run the commands in the 'Verify..' section of that article and make sure the rest of your configuration is correct.

[Narev]

Thank you, i changed my host file to the following:

127.0.0.1 localhost.localdomain localhost
192.168.200.30 zimbra-test.ourdomain.nl zimbra-test

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

and i also changed my /etc/hostname to match the external hostname.

However after i reset my zmservername with zmsetservername -n zimbra-test.ourdomain.nl and reboot the server with zmcontroll restart i get the following:

zimbra@zimbra-test:~$ zmcontrol restart
Host zimbra-test.ourdomain.nl
Stopping stats...Done.
Stopping mta...Done.
Stopping spell...Done.
Stopping snmp...Done.
Stopping archiving...Done.
Stopping antivirus...Done.
Stopping antispam...Done.
Stopping imapproxy...Done.
Stopping memcached...Done.
Stopping mailbox...Done.
Stopping convertd...Done.
Stopping logger...Done.
Stopping ldap...Done.
Host zimbra-test.ourdomain.nl
Starting ldap...Done.
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Starting logger...Failed.
Starting logswatch...ERROR: account.NO_SUCH_SERVER (no such server: zimbra-test.ourdomain.nl)
zimbra logger service is not enabled! failed.


Starting convertd...Done.
Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Done.
Starting stats...Done.

After this i tried to connect with the mail webaccess by http://zimbra-test.ourdomain.nl but this still does not work? So i was wondering could that be any of the errors that are provided in the above log or is there something else wrong?

[phoenix]

Just for confirmation please post the output from the Split DNS/Verify... section so we can check it.

[Narev]

dig zimbra.cape-groep.nl mx

; <<>> DiG 9.4.2-P2.1 <<>> zimbra.cape-groep.nl mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16800
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

;; QUESTION SECTION:
;zimbra.cape-groep.nl. IN MX

;; ANSWER SECTION:
zimbra.cape-groep.nl. 6126 IN MX 100 zimbra-test.cape-groep.nl.

;; AUTHORITY SECTION:
cape-groep.nl. 8475 IN NS ns.echelon.nl.
cape-groep.nl. 8475 IN NS nsx.echelon.nl.

;; ADDITIONAL SECTION:
zimbra-test.cape-groep.nl. 6126 IN A 217.119.233.149
ns.echelon.nl. 162 IN A 217.119.226.66
nsx.echelon.nl. 162 IN A 91.190.97.2

;; Query time: 2 msec
;; SERVER: 192.168.200.1#53(192.168.200.1)
;; WHEN: Wed Sep 22 14:30:01 2010
;; MSG SIZE rcvd: 157

dig zimbra.cape-groep.nl any

; <<>> DiG 9.4.2-P2.1 <<>> zimbra.cape-groep.nl any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9742
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

;; QUESTION SECTION:
;zimbra.cape-groep.nl. IN ANY

;; ANSWER SECTION:
zimbra.cape-groep.nl. 6016 IN MX 100 zimbra-test.cape-groep.nl.

;; AUTHORITY SECTION:
cape-groep.nl. 8365 IN NS ns.echelon.nl.
cape-groep.nl. 8365 IN NS nsx.echelon.nl.

;; ADDITIONAL SECTION:
zimbra-test.cape-groep.nl. 6016 IN A 217.119.233.149
ns.echelon.nl. 52 IN A 217.119.226.66
nsx.echelon.nl. 52 IN A 91.190.97.2

;; Query time: 2 msec
;; SERVER: 192.168.200.1#53(192.168.200.1)
;; WHEN: Wed Sep 22 14:31:51 2010
;; MSG SIZE rcvd: 157

host $(hostname)

zimbra-test has address 192.168.200.30

/etc/resolv.conf

search cape-groep.dmz
nameserver 192.168.200.1

[phoenix]

There is a problem with those results returned by the dig command, your DNS A record does not point to the LAN IP address (it points, I guess, to the public IP and it should never do that as it can't be resolved from your LAN) of your Zimbra server - it should. Zimbra (actually Postfix) requires that it's IP address can be resolved by a DNS lookup so it can correctly deliver the mail - you need to fix your DNS record.

[Narev]

i have consulted with our network admin and according and based on that it appeared i have been feeding you some wrong info so i updated my above post. We actually do have an MX record set for zimbra which is zimbra.cape-groep.nl, does that mean it will conflict with any of my previous settings? I also noted that if i dig on zimbra.cape-groep.nl it still returns the external ip adress, does that mean our dns is still directing it wrongly?

[phoenix]

Originally Posted by Narev

i have consulted with our network admin and according and based on that it appeared i have been feeding you some wrong info so i updated my above post. We actually do have an MX record set for zimbra which is zimbra.cape-groep.nl, does that mean it will conflict with any of my previous settings? I also noted that if i dig on zimbra.cape-groep.nl it still returns the external ip adress, does that mean our dns is still directing it wrongly?

You are now using a subdomain for your DNS resolution of the Zimbra server and your hosts file now needs to change to reflect that. In your hosts file you have the FQDN of your server which consists of your hostname and the domain name, as you're now using a subdomain the entry in your hosts file should look like this:

192.168.200.30 mail.zimbra-test.ourdomain.nl mail

Note that I have added the hostname 'mail' to your entry, that's just an arbitrary choice and can be anything you like. You will also need to modify your DNS records to reflect that change and, as I mentioned above, your IP address should be the LAN IP of the Zimbra server and not your Public IP address. In addition and assuming that you're not trying to run a Split Domain, your domain name on the server should now be "zimbra-test.cape-groep.nl", if you are trying to run a Split Domain then follow the wiki article.

[Narev]

Well we finally got it working eventhough many many people have said and stated it befor DNS settings are indeed important The solution for us was the following:

/etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.200.30 zimbraserver.ourdomain.nl zimbraserver

/etc/hostname
zimbraserver

/etc/resolv.conf
search cape-groep.dmz
nameserver 192.168.200.1

Then also importat were our zimbrasettings.

our servername was:

zimbra-test.ourdomain.nl

our domainname was:

zimbra.ourdomain.nl

The last part was also were we went wrong, because we used a subdomain our domain actually was different then the suffix from our servername. This is probebly also why it didn't work with the setservername command. I bet that this command actually tries to retrieve the domain from the servername, hench why it would not work.