mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 06:05:55 +03:00
[GH-ISSUE #662] DNS Verification Failing #473
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#473
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nickrupert7 on GitHub (Jul 20, 2024).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/662
Hello, I have been using anonaddy/addy.io for over a year and a half now. Until recently, it has worked just fine, but now, I am suddenly receiving DNS verification errors on my custom domain with the following error messages:
CNAME dk1._domainkey record not found. This could be due to DNS caching, please try again later.CNAME dk2._domainkey record not found. This could be due to DNS caching, please try again later.The past few days, it's been on and off - One minute it will verify, then that evening, I'll get the email that verification is failing again, and when I manually recheck, it just keeps failing.
I did recently migrate my domain name registration and DNS to AWS Route 53, but this was over a week ago, and I can confirm that all of the correct records ARE in my Hosted Zone. 3rd party DNS query tools also always return the correct records. The TTL on the relevant records in both the old and new DNS were 300s (5 mins), so it really shouldn't be a caching issue several days later like this.
This same issue was also referenced in https://github.com/anonaddy/anonaddy/issues/491, but no solution was ever given because it seemingly resolved itself.
@willbrowningme commented on GitHub (Jul 22, 2024):
Please could you send me an email with details of your domain so that I can have a look into this?
@nickrupert7 commented on GitHub (Jul 22, 2024):
Email sent. Thanks!
@willbrowningme commented on GitHub (Jul 26, 2024):
It seems this issue was caused by an incorrect DNSSEC configuration after recently changing DNS Providers.
@nickrupert7 commented on GitHub (Jul 28, 2024):
Confirming for future reference: Enabling DNSSEC on my domain did appear to resolve the issue. If you find yourself in the same boat as me, please try enabling DNSSEC and everything should validate correctly!
Thank you @willbrowningme !