- Newest
- Most votes
- Most comments
Based on the information provided in your images and question, it appears you're having trouble verifying your domain records for email services (likely using Mailgun with AWS Route 53). There are a few potential reasons why your domain records may not be verifying:
-
DNS Propagation: After adding or modifying DNS records, it can take up to 24-48 hours for the changes to propagate fully across the internet. If you've recently added the records, you may need to wait longer for verification to complete.
-
Nameserver Mismatch: Ensure that the nameservers listed in your domain registration match those in your Route 53 hosted zone. If there's a mismatch, your DNS changes won't be authoritative and may not be recognized.
-
Record Formatting: Make sure the TXT records are formatted correctly. Some DNS providers automatically modify record values (e.g., converting to lowercase), which can cause verification issues.
-
Incomplete Records: Verify that you've added all required DNS records for your email service. Some services require multiple records (e.g., TXT, MX, CNAME) for full verification.
-
Subdomain Issues: If you're trying to verify a subdomain, ensure you've created the records in the correct zone and with the correct fully qualified domain name.
To troubleshoot:
- Double-check that the nameservers in your domain registration match those in your Route 53 hosted zone.
- Verify that all required records are present and formatted correctly.
- Use DNS lookup tools to check if your records are visible publicly.
- Wait at least 24-48 hours after making changes before attempting verification again.
If issues persist after these steps, you may need to contact AWS support or your email service provider for further assistance.
Sources
Domain and Email address verification problems - Amazon Simple Email Service
NS records not matching domain lookup | AWS re:Post
I transferred the domain to Route 53 and created a DNS zone, but unable to verify using txt record. | AWS re:Post
answered 2 years ago
Please check your Hosted Zone Details on the Zone. I suspect they do NOT match the NS records in your Zone.
Can you share the Name servers there?
Relevant content
asked 2 years ago
asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
