DKIM is not generated in DNS Records any more

Community Support Mail
1

Hello everyone.

Since the last update I am noticing that when creating a new user, entering that user, then creating a site/domain and activating the “dns support” and “mail support” options, after the last update (at least since I noticed) it is not auto-generating the DKIM in the DNS Records.

Even after activating the “DKIM Support” option in the email section of that domain.

Does it happen to anyone else? I have a production server and a small test server, the same thing happens on both.

Thanks and regards!

image
image870×431 27.6 KB

PS: after several “uncheck->save/check->save/uncheck->save/check->save” in the “Support DKIM” in the mail option, it’s generated and added to DNS Records. (in both servers)

2

No. I just checked last update and new install and the DKIM generation is in there. You might want to peruse your templates.

image
image1062×401 35.1 KB

3

What’s template are you referring? Tell me to check it please. Thanks

4

HestiaCP uses DNS templates to standardize zone configurations, stored in /usr/local/hestia/data/templates/dns/. These templates contain placeholders (like %ip% or %domain_idn%) that are replaced with user-specific variables when a domain is added or rebuilt.

Available Built-in Templates:

  • default: Standard configuration for most use cases.

  • default-nomail: Standard configuration excluding mail records.

  • gmail: Configures records for Google Workspace.

  • office365: Configures records for Microsoft 365 (Exchange).

  • zoho: Configures records for Zoho mail.

  • child-ns: Used when the domain acts as a name server.

Management and Customization: Administrators can update templates using the command v-update-dns-templates. Custom templates can be created in the active templates directory and applied by rebuilding domains with v-rebuild-dns-domains user. When editing a DNS zone in the UI, users can select the appropriate template from the dropdown, though granular permission controls to restrict this selection are currently a feature request.

5

well.. I recheck my local templates with github version and no differences.. also the script v-add-dns-record so maybe was a temp error, in both servers.

Thanks for your time @durglewankelshteim

6

You can test it by adding a domain with the DNS option checked like test1.mydomain and see what it creates. All the best!

7

Yes, I have tried several ways.

  • Creating domain without DNS and without email (Then creating both)
  • Creating domain with DNS and then email
  • Creating domain without DNS but with email.

But don’t worry, in the latest hestia update 1.9.8 I found that it was resolved (at least it didn’t happen again). I was looking at the changelog and maybe it is due to a fix in v-list-mail-domain-ssl

Thanks again for the follow-up.

8

Glad it is now resolved for you. All the best!