Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with aliased domains and turning off dns and enabling dns #173

Open
kdovale opened this issue Mar 1, 2024 · 0 comments
Open

Issue with aliased domains and turning off dns and enabling dns #173

kdovale opened this issue Mar 1, 2024 · 0 comments

Comments

@kdovale
Copy link

kdovale commented Mar 1, 2024

Describe the bug
If you have a domain that is aliased by another domain, ie domain1 is the primary and you alias domain2 to the first, it adds a email domain record under domain1. If you turn off dns for domain2 and enable it again, the mail records are never restored in dns, and thus breaking mail for the aliased domains.

To Reproduce
Steps to reproduce the behavior:

  1. add domain1, and add a second domain2 and alias it to domain1 email
  2. Click on email domains select domain1 and check there is a header for doman2 defined there.
  3. open domains select domain 2 and check the dns records there is mail records, then disable the dns zone and re-enable it'
  4. Then check domains2 records again the mail records are missing.
  5. then goto domain1 mail domain remove the header for the domains2 and re-add it back
  6. check the domain2 domain records the mail records are put back

Expected behavior
I would assume that the system would pick up the domain is aliased and restore the dns records automatically, the issue here is some clients have like 10 domains aliased to a primary, and if you by mistake have disabled and reenabled the domain you assume the records are restored, but in fact they are not, leaving the aliased domains broken and not working.

SolidCP Info

  • SolidCP Version: [ 1.4.9]

We picked this up when we changed the ip addresses on our mail servers for some users, we disabl3ed and re enabled the zones as this recreates the updated records if its a mail zone by itself without issue, however when we came across the aliased domains we then realized the mail records had not been recreated automatically, and had to goto the primary domains mail domain, remove the aliased domains and re-add them back again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant