Ses domain verification10/2/2023 The reason this is the fix is simply because Route 53 is who you have already - at some point in the past - chosen as your authoritative DNS hosting provider. The fact that these are both AWS services is coincidental. ![]() In the interest of not confusing future readers, the reason this entry goes in Route 53 is not because of any necessary connection between SES and Route 53. Verify the domain if it hasn’t already by following the instructions at Verifying Domains in. Verify that the parent domain of the MAIL FROM domain is validated in the list of domains. Select Domains from the Identity Management section of the navigation pane. Your nslookup should start working as expected and SES should have no trouble validating your record, after that. Login in to access the Amazon SES console. In the Route 53 console, find the Hosted Zone for this domain with matching name servers, and add this record there. Registrars have, in my opinion, confused this issue for many people by bundling free authoritative DNS hosting with paid name regstration services, even though these are rightfully two independent service offerings.Īt some point, you switched your DNS hosting over to Route 53, and for this reason, Route 53 is where you need to create this new record. ).Īny entries you make in the registrar's DNS record management console will have no effect at all if the registrar's DNS servers aren't the ones your domain is actually using. Your domain is evidently registered with Register365, but your authoritative name servers are actually AWS Route 53 name servers (e.g. If Amazon SES is unable to detect the record within 72 hours, the domains verification status changes to 'Failed.' In that case, if you still want to verify the domain, you must restart the verification process from the beginning. ![]() on a set of name servers that you aren't actually using to host the DNS for this domain. When Amazon SES detects the record, the domains verification status changes to 'Success'. ![]() For solutions to DKIM-related issues, see Troubleshooting DKIM problems in Amazon SES. You're creating the DNS record in a place where nobody but you can actually see it. This section contains the following topics that may help you when you encounter problems: For information about domain verification problems that you might encounter, see Domain and Email address verification problems.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |