(The repository with code is here: https://gitlab.com/aerique/dnsdist-ens/. The links to code have not been fixed.)
This is the third exploration of resolving ENS through traditional DNS servers. The previous two articles have used DNSdist, which is a DNS load balancer. This time we’re using an authoritative server (“auth”) for several reasons:
(The repository with code is here: https://gitlab.com/aerique/dnsdist-ens/. The links to code have not been fixed.)
I’m putting this out here while it is still in a draft state since I have other stuff to do and it might be a while before I get back to this. This article has not been proof-read by others and might have incorrect statements (especially about DNS and the auth). It is also somewhat disjointed and lacks a point. Still, even in this state it might be useful to others.
(The repository with code is here: https://gitlab.com/aerique/dnsdist-ens/. The links to code have not been fixed.)
This article is an update to an article I wrote about one-and-half years ago. My intention was to continue with it sooner but life got in the way.
(The repository with code is here: https://gitlab.com/aerique/dnsdist-ens/. The links to code have not been fixed.)
(Also, this article was written before The Merge and using Geth is not as straightforward anymore as shown in here.)
The goal of this article is to show how one, with a little extra code, can query a DNS server for an Ethereum Name Service (ENS) domain and get a wallet address back.