Disappearing Mail Record from DNS Configuration After Hestia Update

[slavovstudio]

Hello,
I have the following issue: after every update of Hestia, the A record for mail disappears from the DNS configuration. On some domains, it has been duplicated 10 times.
I checked the template files, and everything seems fine there.
Has anyone experienced a similar issue, and how could it be resolved?

[justadri]

Hi sorry to revive an old thread, but I am having the exact same issue and I see a solution was never proposed.

After every Hestia update the “A” record for mail.domain.xyz gets deleted for every one of my DNS domains. I think it might be occurring as part of the “rebuild mail domain” operation?

Possibly relevant:

• In my Hestia configuration, under “Mail Server”, I have “Webmail Alias” set to “mail” rather than the default “webmail”.
• When I am looking at the Mail Domains screen and click the “DNS Records” icon next to any of the domains, it shows the mail.domain.xyz A records twice.

Probably less relevant:

• I am running on Ubuntu 22.04, with Hestia installed using the official installer on top of a default OS install.
• I am running a bind9 cluster with 2 other hosts; the mail host is the DNS master

I appreciate any ideas on where to look (DNS templates maybe?). I host 8 mail domains that users rely on and have downtime after every update until I manually re-add the A records.

Thank you!

[nagr]

I am having the exact same issue that justadri is describing, with the same observations.
Serve this message as a bump, maybe we can get some attention on the issue.

May be related to Hestia updates change custom DNS records

[nagr]

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.

[Fix] Disappearing Mail Record from DNS Configuration After Hestia Updates

[Anuril]

This issue merits further investigation. Can check what domain template you have selected in the dns domain, and provide the template ?

You can find it here: /usr/local/hestia/install/common/templates/dns

[nagr]

I have replied to the comments in the github pull request and provided more explanations.

Regarding the DNS template, the issue is materializing for me using “default.tpl”

ID='1' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns1%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='2' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns2%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='3' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns3%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='4' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns4%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='5' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns5%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='6' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns6%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='7' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns7%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='8' RECORD='@' TYPE='NS' PRIORITY='' VALUE='%ns8%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='9' RECORD='@' TYPE='A' PRIORITY='' VALUE='%ip%' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='10' RECORD='www' TYPE='CNAME' PRIORITY='' VALUE='%domain%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='11' RECORD='ftp' TYPE='CNAME' PRIORITY='' VALUE='%domain%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='12' RECORD='mail' TYPE='A' PRIORITY='' VALUE='%ip%' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='13' RECORD='webmail' TYPE='CNAME' PRIORITY='' VALUE='mail.%domain%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='14' RECORD='@' TYPE='MX' PRIORITY='0' VALUE='mail.%domain%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='15' RECORD='@' TYPE='TXT' PRIORITY='' VALUE='"v=spf1 a mx ip4:%ip% -all"' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='16' RECORD='_dmarc' TYPE='TXT' PRIORITY='' VALUE='"v=DMARC1; p=quarantine; pct=100"' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='17' RECORD='_submission._tcp' TYPE='SRV' PRIORITY='1' VALUE='0 587 mail.%domain%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='18' RECORD='_imap._tcp' TYPE='SRV' PRIORITY='1' VALUE='0 143 mail.%domain%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='19' RECORD='_imaps._tcp' TYPE='SRV' PRIORITY='1' VALUE='0 993 mail.%domain%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='20' RECORD='_pop3._tcp' TYPE='SRV' PRIORITY='1' VALUE='0 110 mail.%domain%.' SUSPENDED='no' TIME='%time%' DATE='%date%'
ID='21' RECORD='_pop3s._tcp' TYPE='SRV' PRIORITY='1' VALUE='0 995 mail.%domain%.' SUSPENDED='no' TIME='%time%' DATE='%date%'

[nagr]

Hello! If any further clarifications are needed from the maintainers, please ping me on the github PR. Let’s get this going so we can fix this bug for the next release!

[Fix] Disappearing Mail Record from DNS Configuration After Hestia Updates

[nagr]

I’ve catched up a bit on the repositories’ (and more specifically, the maintainers’ available dedication) news. Considering all the aspects that hestia covers and what the priorities have been focused on for the next release, I shall request some attention to this issue.

When the new update rolls out, some installations may be impacted by this bug and the DNS records for the mail.domain.tld will disappear on domains affected by the described configuration. Thus, given the severity of the bug, I strongly recommend selecting this issue to be fixed before the next release.

@sahsanu @Lupu @eris

In case you need any additional help or clarifications, I’m here to shed some more light on my PR’s code and why I’ve made the changes that I submit.

[sahsanu]

@nagr Sorry, I’m not a dev and I can’t merge PRs.

[nagr]

Hello,
Just as expected, the new update rolled out and it removed the DNS A records for mail.domain.xyz for all domains that matched the conditions. This has a major outage for us providers, so please reconsider including this year-old PR in the next release.

[Fix] Disappearing Mail Record from DNS Configuration After Hestia Updates (#5074)

I know the maintainers time is limited, but this bug breaks the email service (because of the missing A record for mail) after each update.

@sahsanu @Raphael @eris

[sahsanu]

I don’t approve/merge PRs

[nagr]

So, please, can you contact any of the maintainers to shed some attention on this issue?

[Raphael]

We are already on it, 1.9.6 will follow today.

[jekasumy]

Thank you very much!