Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the status of ENSIP-6 from Stagnant to Draft and enhances compatibility with DNS without requiring changes to the DNS resolver profile. Instead, it establishes a better convention for translating ENS nodes and record sets to DNS.
The main improvement involves treating record sets as part of the top-level domain zone which may work better for .eth and enables several useful features:
(nick.eth, nick.eth, CNAME)
).This approach makes it theoretically possible to export all ENS nodes implementing this ENSIP into a DNS-compliant zone that can be consumed by standard DNS software with support for zone transfers ... etc.
There are other ways to do this, most come with their own trade-offs. This proposal does not require changing any contracts, but instead provides a clearer convention for those wanting to build DNS integrations for ENS but of course I'm open to other ideas. Thanks!