Hello everyone!
I have one server as a web server (IP A.A.A.A) and another as a mail server (IP B.B.B.B).
The DNS server is also on the web server, and in the website records, I have the “mail” and “webmail” subdomains pointing to the email server IP (IP B.B.B.B).
This is what happens: every time HestiaCP is updated, the update changes the “webmail” IP (IP B.B.B.B) to the web server IP (IP A.A.A.A).
This only happens with the “webmail” subdomain; the “mail” subdomain correctly retains the mail server IP.
I can easily fix this by manually changing the “webmail” IP, but:
Is there anything I’m doing wrong or what can I do to prevent this change with each Hestia update?
I’ve taken a look at the code and I think that I’ve identified the problem.
A pull request has been submitted to the repository for the maintainers to look at.
Hi Eduardo, I don’t think you are doing something wrong, I have experienced similar issue, I have 2 servers, in my case main server has everything, second server is a fully installation too but I use it as second DNS, to get remote backups and some test… I have some domains on main server that points to different IPs, one time I have reinstall 2nd server from scratch and when backup was restored that same thing happends, A records with different IPs were changed to actual server IP, as you mentioned way to fix it was either manually or run DNS backup restore only for the affected domain.
As alternative option, have you considered manage DNS records through Cloudflare Free version ?
As discussed in my review of the code of @nagr - your issue doesn’t have to do anything with that. The Issue stems from you enabling webmail on the webdomain:
