-
Notifications
You must be signed in to change notification settings - Fork 7
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
Support to disable mx verification record #3
Comments
Just ran into the same issue. The practical impact of this is that you can't transfer from another DNS provider to Route53 if you no longer have your verification record as it doesn't seem to be possible to generate it again after the domain is verified. |
Same here, ran into the same issue. Would be great if Google provided a way to get the MX verification record. |
I'm not sure if I'm facing the same issue, but when going through the GMail activation process for Google Workspaces, the wizard nag screen wants me to not have an MX verification record of any kind, preventing me from using this module. FWIW: GSuite required the apex text, but not the MX validation record. So AFAICT you can't use this module for new Google Workspace installs. (You can always add the MX back later I guess?) |
Thanks for the awesome work, I will use the module but for the time being I will not add the MX verification module, I had to fork/clone to local project so I can had support for this.
If you are interested in this feature to disable the MX verification record I will gladly open a PR.
The text was updated successfully, but these errors were encountered: