Automatic SSL & Mail Certificate Reconciliation After DNS Propagation

Mar 24, 2026


Post by

Fatih AYHAN

Status

open

Currently, EEnos performs SSL and mail certificate provisioning only at domain creation time. If the domain is added before DNS is pointed to the server, the system skips SSL setup and does not retry later.

This creates a significant operational issue:
- Domains are often created before DNS propagation is completed
- SSL is not provisioned during initial setup
- Even after DNS is correctly pointed, EEnos does not retry SSL generation
- Mail services may continue using invalid or missing certificates
- Administrators are forced to manually regenerate SSL certificates, restart mail services, and verify configurations via SSH

Expected behavior:
- If DNS is not ready at domain creation, mark SSL as pending
- Periodically retry SSL issuance for web and mail
- Automatically apply certificates once DNS resolves correctly
- Reload or restart required services such as nginx, dovecot, and postfix
- Show accurate status in the UI
- Provide a manual Retry SSL button


Comments :
Fatih AYHAN an hour ago

This issue already caused multiple operational problems in real-world usage.

Domains are often created before DNS propagation is completed. When this happens, SSL is skipped and never retried, which forces manual intervention via SSH.

This is not an edge case, it is a very common workflow in hosting environments.

A reconciliation mechanism is critical for production reliability.


Copyright © Eenos
Built on Python Developed by Eenos Team