🤖
LNS Documentation
  • Introduction
  • Terminology
  • Frequently Asked Questions
  • Tokenomics
  • LNS Deployments
  • Registrar Frequently Asked Questions
  • Deploying LNS on a Private Chain
  • DNS Registrar guide
  • Bug Bounty Program
  • ENS Improvement Proposals
    • ENSIP-1: ENS
    • ENSIP-2: Initial Hash Registrar
    • ENSIP-3: Reverse Resolution
    • ENSIP-4: Support for contract ABIs
    • ENSIP-5: Text Records
    • ENSIP-6: DNS-in-ENS
    • ENSIP-7: Contenthash field
    • ENSIP-8: Interface Discovery
    • ENSIP-9: Multichain Address Resolution
    • ENSIP-10: Wildcard Resolution
    • ENSIP-11: EVM compatible Chain Address Resolution
    • ENSIP-12: Avatar Text Records
  • Dapp Developer Guide
    • LNS Enabling your DApp
    • LNS Libraries
    • Working with LNS
    • Resolving Names
    • Managing Names
    • Registering & Renewing Names
    • LNS Front-End Design Guidelines
    • LNS as NFT
  • Contract API Reference
    • Name Processing
    • Registry
    • ReverseRegistrar
    • PublicResolver
    • .bch Permanent Registrar
      • Registrar
      • Controller
    • DNS Registrar
  • Contract Developer Guide
    • Resolving Names On-chain
    • Writing a Resolver
    • Writing a Registrar
    • LNS Support Chat
Powered by GitBook
On this page
  • Introduction
  • Steps
  • Step 1 Setting up DNSSEC signing
  • Step 2: Adding a TXT record
  • Step 3: Registering the name into LNS
  • Step 4: Go to the manager
  • FAQ
  • Can I register any DNS domains through LNS app?
  • If I own myname.xyz DNS name, can I claim for myname.eth ?
  • Once I register the domain, how can I transfer or delete ownership?
  • Can I register my DNS subdomain?
Edit on GitHub

DNS Registrar guide

PreviousDeploying LNS on a Private ChainNextBug Bounty Program

Last updated 3 years ago

Introduction

DNSSEC (The Domain Name System Security Extensions) establishes a chain of trust from the root key which is signed by ICANN (.) and down through each key. Given DNSSEC is enabled and an ETH address is put into the subdomain of the domain you own (eg: _ens.yourdomain.tld), LNS manager allows anyone to submit the hash of the chain to DNSSEC Oracle smart contract

Steps

Step 1 Setting up DNSSEC signing

When you first land on LNS manager, you will see something like below.

If your DNS provider already supports DNSSEC-signed domains, all you do is enable the option on the DNS manager.

Whatever provider you need, make sure you select RSA signatures and SHA256 hashing.

Step 2: Adding a TXT record

The DNS Registrar on LNS looks for a TXT record with a specific name and format in order to verify what smartBCH address should be given ownership of the domain. To claim ownership of mydomain.xyz, create a TXT record in your DNS zone, _ens.mydomain.xyz, with text data of the form a=0x1234..., where 0x1234... is the smartBCH address you want to give control of the LNS record to.

Step 3: Registering the name into LNS

Once you get to this stage, you can complete the rest from LNS manager. Simply press "Register" and send the transaction.

Step 4: Go to the manager

FAQ

Can I register any DNS domains through LNS app?

If I own myname.xyz DNS name, can I claim for myname.eth ?

Once I register the domain, how can I transfer or delete ownership?

Unlike .eth permanent registrar, there is no notion of registrant which can transfer the ownership of the controller. If you want to transfer the ownership to any address other than the currently registered address, please update the corresponding DNS record from your DNS manager and click "Transfer" from our LNS manager.

We currently haven't enabled the ability to delete the ownership. Having said that, you can achieve the same effect if you set the owner record to a= 0x0000000000000000000000000000000000000000 then click "Transfer" from the LNS manager.

Can I register my DNS subdomain?

No. DNSSEC registration is only enabled for the second level domain (eg: yourname.xyz). If you want to create subdomain.yourname.xyz, then click "Subdomains" tab of our manager and create it from LNS manager just like other subdomains under .eth.

If they don’t, you’ll need to migrate to someone who does. We recommend either or . EasyDNS’s setup guide for DNSSEC is , while Google’s is .

Technically speaking, can be supported. Some TLDs (ceo, .art, .club, .luxe and .kred) are operated by each DNS registry.

You may be confused with . Under DNSSEC integration, you can only claim for the correspondent LNS name with the same top level domain (TLD). .eth is managed completely separately.

EasyDNS
Google Cloud DNS
here
here
over 90% of domains
short name reservation process
step1: dnnsec not enabled
sha|690x468
step2: add text
step3: owner submit proof
step4: owner