ENS (.eth) is not resolving correctly

Hi,

I'm a dev from ENS Labs. I reported a year or so ago that the .eth resolution was not working. It still seems to be the case, and we'd like to help fix it and implement it properly. Based on my knowledge, NextDNS relies on an obsolete ENSIP-6 standard for resolving .eth domains. Websites on ENS resolve differently from traditional DNS, through a "Content-Hash" field, which contains an IPFS/Arweave/Swarm reference.

eth.limo is one of the teams providing an ENS gateway, they have an open source implementation for a DNS resolver: https://github.com/ethlimo/limo-web3-dns

If you're interested in integrating ENS into NextDNS, please let us know and feel free to contact one of our folks:

Simon (DevRel) - simon@ens.domains, https://x.com/schmid_si, https://t.me/schmidsi

v7rtl (Web Developer) - nextdns.vgxxq@fastmail.com, @monogram:bladerunn.in on matrix