mirror of
https://github.com/abh/geodns.git
synced 2026-04-27 03:45:53 +03:00
[GH-ISSUE #138] Request for DNSSEC Support #96
Labels
No labels
bug
bug
enhancement
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/geodns#96
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 @MiguelFGM on GitHub (Oct 27, 2023).
Original GitHub issue: https://github.com/abh/geodns/issues/138
Hello @abh,
I would like to express my interest and advocate for the implementation of DNSSEC (Domain Name System Security Extensions) support in GeoDNS. DNSSEC is crucial for ensuring the integrity and authenticity of DNS responses, which is fundamental in maintaining a secure and trustworthy domain name system.
Implementing DNSSEC would greatly enhance the security posture of GeoDNS by preventing DNS spoofing and other related attacks that could mislead or misroute users. This implementation would also align GeoDNS with modern security standards and practices, making it a more robust and reliable solution for many organizations and individuals alike.
I understand that implementing DNSSEC might be a significant undertaking, but the security benefits and the enhanced trust it would bring to the system are well worth the effort. Additionally, DNSSEC support is becoming increasingly expected within the community, and adding this feature would undoubtedly elevate GeoDNS's standing and utility in the ecosystem.
I am hopeful that the team will consider this request and would be more than willing to discuss further or contribute in any way I can to help make DNSSEC support a reality in GeoDNS. Thank you for your time and consideration.
Best regards!