As far as I know, .et is the TLD of Ethiopia, and .eth may be confused with .et, so ENS DAO could not apply .eth as a TLD.
How about submitting .ens TLD application to ICANN?
If ENS DAO owns .ens TLD, ENS user can set traditional DNS information on-chain, such as IP . On-chain traditional DNS information could be synchronized to traditional DNS service by an off-chain service.
For example: The admin of www.abc.eth can set the A Name of www.abc.eth to 202.121.1.12. The website https://www.abc.ens can be opened on any browser.
Reference:
1 Like
This is a interesting suggestion, I support this in some extent. But before that, I want to say:
This is not accurate. I believe ENSDAO still have the opportunity to be the operator of the .eth tld. We can find it from @lucemans 's tweet: https://twitter.com/LucemansNL/status/1717944079281983573
And .eth is absolutely the first option for now, because the difference between .eth and .ens is much bigger than the difference between .ens and any other tld that is available.
2 Likes
Seems like .eth tld could totally be an option - see list of all the brands that have applied or received domain names here: Root Zone Database
I would be willing to help with this. Seems like we could tie the ENS .eth to the DNS .eth and have them renew together. Then use the Godaddy ENS link for payments!
ICANN is web2 tech, ~ENS CAN’T play by their rule books…
only way out is altrooting OR some $big web2+3 remix of ENS+ICANN.
https://www.icann.org/compliance/complaint
Rights Protection Mechanism(RPM)
A mechanism that helps safeguard intellectual property rights in the Domain Name System. RPMs include the Uniform Domain Name Dispute Resolution Policy (UDRP), Uniform Rapid Suspension (URS), and Trademark Post-Delegation Dispute Resolution Procedure (Trademark PDDRP).