<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ENS on Nalar</title>
    <link>https://nalar.dev/tags/ens/</link>
    <description>Recent content in ENS on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/ens/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Web3 Domains Do Not Replace DNS: The ENS Resolution Boundary</title>
      <link>https://nalar.dev/web3-domains-do-not-replace-dns-ens-resolution-boundary/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/web3-domains-do-not-replace-dns-ens-resolution-boundary/</guid>
      <description>&lt;p&gt;A name such as &lt;code&gt;alice.eth&lt;/code&gt; looks like an Internet domain, but its resolution path is not the same as &lt;code&gt;example.com&lt;/code&gt;. A conventional domain normally enters the Domain Name System, where resolvers follow the DNS hierarchy to obtain records such as &lt;code&gt;A&lt;/code&gt;, &lt;code&gt;AAAA&lt;/code&gt;, &lt;code&gt;MX&lt;/code&gt;, or &lt;code&gt;TXT&lt;/code&gt;. An ENS name enters a different naming system whose authoritative state is expressed through Ethereum smart contracts.&lt;/p&gt;&#xA;&lt;p&gt;That distinction is the practical boundary behind many claims about &amp;ldquo;Web3 domains.&amp;rdquo; The name can be globally meaningful to software that implements ENS resolution while remaining unknown to a DNS resolver. A browser, wallet, or dApp therefore needs an ENS-aware resolution path before &lt;code&gt;.eth&lt;/code&gt; can behave like a useful name.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
