Just install Zimbra

[kdmiller45]

Just installed this server in the morning, looks sharp. enough get to the point huh
O/S Ubuntu 18.04 Server (not workstation)
installed the Zimbra Collaboration Open Source version

I am unable to ping gmail.com answer is "ping: gmail.com: Temporary failure in name resolution

maybe something in host name really not sure, that's why I'm here

The mxtools website says DMARC record published and found, DNS Record Published and found, I can get to admin console via the domain_name:7071, I can also get to webmail console, I can ping the domain and telnet to public IP:25

just can not send or receive email

Keith

[phoenix]

It's a firewall or DNS problem and nothing to do with zimbra, do an internet search for the error message.

[AnZAdmin]

Well it is possible that it is a Zimbra problem. I installed a 8.8.15.GA.3869.UBUNTU18.64 UBUNTU18_64 FOSS edition, Patch 8.8.15_P12 on Ubuntu 18.04.5.
If I compare unbound /opt/zimbra/conf/unbound.conf from the new server with an old one the difference is forward-addr. On the new server it points to systemd-resolved -> 127.0.0.53. On the old server to my internal DNS servers.

Code: Select all

zmprov getServer `zmhostname` | grep DNSMasterIP

Shows the difference.

Based on this
https://wiki.zimbra.com/wiki/DNS_cachin ... (dnscache)
you can change the DNS servers.

Should zimbraDNSMasterIP point to 127.0.0.53?

[phoenix]

You can point that to any DNS server you choose, as I don't use the ZCS DNS server my setting point to my LAN DNS cluster.

BTW, I assume you meant "127.0.0.1:53"?

[AnZAdmin]

Thanks, I know I already did that. And nope 127.0.0.53 is correct. That's systemd-resolved IP for DNS access directly.
My input was to give ideas for others with this issue.

An other alternative could possibly be to uninstall (or not install) zimbra-dnscache.
NOTE: SHOULD NOT BE INSTALLED ON SYSTEMS THAT ALREADY HAVE BIND OR OTHER DNS SERVICES INSTALLED.
Overlooked that part in the referenced manual. Though I didn't try that.

Besides, I also hoped to get a good fix without circumventing resolved.
It seams that Zimbra intended to allow a systemd-resolved / dnscache (unbound) installation. If not why would the setting in zimbraDNSMasterIP point to 127.0.0.53. This would need less tweaking of Zimbra.

[phoenix]

I don't use DNScache and I run my own PowerDNS server and root hints that don't log anything in addition to RPZ on the DNS servers.

[axslingr]

I never use dnscache either. At the very least I use dnsmasq for testing.