mirror of
https://github.com/nsupdate-info/nsupdate.info.git
synced 2026-04-25 00:25:58 +03:00
[GH-ISSUE #572] ECH Configuration with HTTPS DNS Records on nsupdate.info? #386
Labels
No labels
bug
bug
duplicate
easy
easy
enhancement
enhancement
invalid
needs help
pull-request
scalability
security
task
urgent
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nsupdate.info-nsupdate-info#386
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 @Mosesofmason on GitHub (Jan 9, 2025).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/572
I am writing to inquire about the possibility of configuring Encrypted Client Hello (ECH) using the *******.nsupdate.info DDNS service. As I understand, ECH requires an HTTPS DNS record to be properly set up. However, I could not find documentation regarding whether nsupdate.info supports the configuration of this specific DNS record. I would like to know:
Does nsupdate.info currently support HTTPS DNS records?
If so, could provide guidance, steps, or examples for setting up the record to enable ECH?
Are there any known limitations or alternative methods for achieving ECH support on ******.nsupdate.info domains?
Given the increasing importance of ECH for enhancing privacy in TLS connections, it would be highly beneficial if nsupdate.info could support it.
@ThomasWaldmann commented on GitHub (Jan 9, 2025):
The software currently only supports A and AAAA records.
Guess we already have a ticket about adding other record types, but nobody implemented that yet.