Installation Ubuntu 18.04, ZCS9 -> systemd-resolved vs. zimbra-dnscache

[mtk]

Hi,

when installing Zimbra 9 on Ubuntu 18.04, the installation will note a port conflict on port 53.
Systemd-resolvered shipping with Ubuntu already listens to the port that and zimbra-dnscache wants to open as well.
How would I proceed with that?
Kill systemd-resolveded, which will let the host probably without any dnslookup?
Or not installing zimbra-dnscache? (will it then be able to do SPF/DKIM verification etc...?)

I tried to find resolutions on this on the internet - but could not find anything. Probably the solution is too simple for most people, but me

Thanks for any hints!

[jorgedlcruz]

Hello,
Here a good guide, in Spanish, but with Chrome it does auto translate anyways:

• https://www.jorgedelacruz.es/2020/04/13 ... n-web-app/

If we discuss the DNS issue itself, do the next:

Code: Select all

sudo systemctl disable systemd-resolved
sudo systemctl stop systemd-resolved
sudo rm /etc/resolv.conf
echo "nameserver 1.1.1.1" > /etc/resolv.conf

Then proceed to install dnsmasq as per usual, with this configuration inside:

Code: Select all

server=1.1.1.1
listen-address=127.0.0.1
domain=jorgedelacruz.es
mx-host=jorgedelacruz.es,zcs.jorgedelacruz.es,0
address=/zcs.jorgedelacruz.es/192.168.1.235

Change the hostname and IP of course, then if that, and the hosts are correct, install Zimbra WITHOUT zimbra-dnscache, you do not need it as you have dnsmasq.

Follow the blog step by step and you will have a succesfull Zimbra installed.

Best regards

[mtk]

Hi Jorge,

thank you for your fast reply.
Actually I was reading your blog post before. However, my setup differs since this will not be a lab project with use of public DNS and MX records.
I would not need dnsmasq since zimbra could look up and find the public DNS records. I thought dnsmasq would rather be required for lab environments. Or am I missing a bit?

Kind regards

[jorgedlcruz]

Hello,
I would always recommend dnsmasq to resolve your domain name, MX, and all, immediately, not going to public DNS and have latency (even minimal).

On my good old days serving hundred of domains in Hosting, always used dnsmasq to resolve the known domains.

[mtk]

Will think about it - thanks for the thought-provoking impulse