cDNSd Link Cardano Domains With Handshake and ICANN

Blink Labs CEO Chris Gianelloni don explain how cDNSd fit bridge domains wey blockchain dey manage with the internet infrastructure wey dey already. The open-source resolver dey read domain records from Cardano, dey verify top-level domain ownership through Handshake and dey use ICANN root data for normal addresses.

The presentation follow as dem complete one Catalyst Fund 13 project wey add Handshake support to cDNSd. The project receive 130,500 ADA, and all four development milestones complete by May 2026.

cDNSd Dey Resolve Cardano, Handshake and ICANN Domains

DNS dey convert names wey people fit read like example.com into network addresses wey browsers and applications dey use. The normal system dey operate through ICANN, registries and registrars wey dey in charge of top-level domains like .com, .org and .io.

Handshake dey provide separate blockchain to establish ownership and control of top-level domains. Im protocol dey focus to replace the normal root zone and root servers with cryptographically authenticated ownership records.

cDNSd combine these systems inside one resolver. E dey index domain records wey dem store for Cardano, dey read ownership data from Handshake and dey use ICANN root information for domains wey no dey inside the blockchain-based naming system.

The cDNSd software dey support standard DNS over UDP and TCP, DNS over TLS and DNSSEC validation. E still maintain local database wey contain synchronization state and discovered blockchain data.

Blink Labs dey develop the resolver with Go and dem design am make e fit work inside applications, wallets and network devices. Gianelloni talk say the software fit also compile to WebAssembly, wey fit give applications road to resolve blockchain-based domains without to depend fully on the browser default DNS configuration.

Cardano Smart Contracts Dey Manage Second-Level Domains

The architecture separate ownership of top-level domains from the management of second-level domains. Owner of top-level domain fit provide cryptographic proof of control through Handshake and connect that namespace to matching smart contract for Cardano.

The Cardano contracts define how second-level domains go take create, transfer and configure. cDNSd first go discover the controller contract, then index the registered top-level domains and the contracts wey contain their second-level domain records.

Blink Labs first describe part of the system as marketplace, but Gianelloni talk say the marketplace na mainly reference implementation. The main product na the smart contracts, standards and resolver infrastructure, so that other applications fit integrate without to use one specific Blink Labs website.

The team don also comot from earlier custodial design wey for require make domain owners transfer control give third party. The new model require proof of ownership without to assign custody of the top-level domain to Blink Labs or another intermediary.

Domain owners fit define their own registration conditions, including whether second-level domains fit transferable and who fit modify or remove them. The system fit also delegate selected records back to normal DNS providers.

One organization fit keep ownership and core domain data for Cardano while e assign dynamic subdomains give Amazon, Google or another cloud operator.

The .ada Path Still Depend on ICANN

The Cardano Foundation don previously get 74.5% community support to pursue the .ada and .cardano generic top-level domains. The application window for ICANN 2026 round run from April 30 to August 12, although no public confirmation of approval or delegation for .ada don show.

According to Gianelloni, Blink Labs don also dey work with the owner of .ada for Handshake. The structure wey dem propose go align Handshake-based ownership proof with potential ICANN delegation, while the Cardano Foundation go determine the smart-contract rules wey go govern how .ada domains go dey issue and manage for Cardano.

If ICANN delegate .ada namespace, e fit resolve through standard DNS and people fit access am through normal browsers. Handshake domains wey no get ICANN delegation still need compatible resolver, proxy or dedicated application integration. Secure browser access still introduce certificate and TLS requirements wey pass domain resolution itself.

The current cDNSd release get only Cardano pre-production profiles. Im documentation talk say several requirements for internet-facing production resolver never complete, including full handling of blockchain reorganizations and domain expiration.

For cDNSd, the next technical threshold na verified Cardano mainnet profile and production-grade handling of chain changes and expirations. The separate .ada opportunity depend on ICANN delegation. Na those two boundaries dey separate working pre-production resolver from Cardano-based namespace wey users fit access through everyday browsers.