Setting DNS Records
Last updated
Last updated
Replace all instances of https://dns.decentraweb.org/ with https://dns-goerli.decentraweb.org/ if you'd like to do the steps in Testnet!
If you have just purchased a domain and are still on the checkout confirmation page, click "Manage Name" button and click the domain you just purchased. Otherwise just go to https://dns.decentraweb.org/ > click "My Account" > click the domain you just purchased.
Decentraweb allows you to use your own Smart Contract Resolver. In most cases you should just use Decentraweb's default by clicking the "Use Decentraweb Resolver" button. This will trigger an on chain transaction.
Once this is complete you will see two new additions on the page for setting (IPFS) "Content" and "DNS records". Click the blue edit button on the DNS Records section.
From here you have a dropdown box with a few different DNS record types. Leave the default type on "A" record, set the "value" to the IP address of a webserver you have access to, leave TTL at "1 hour" which is how often the Decentraweb resolver will check for changes.
You can add as many DNS records as you like in one Ethereum transaction to save costs. Once you are complete click the blue "Commit" button to save it to the blockchain.
For Mac and Linux operating systems you can verify your DNS records were properly set on the blockchain via command-line. You can query against Decentraweb's DNS resolver directly. Wait about 30 seconds and run: dig @15.197.159.209 -p 53 yourdomain
Note: Modern browsers expect websites to be hosted on subdomains only. That is why you don't see websites at "com" or "net" or "gov", etc. Additionally Top Level Domains (TLD's) that browser don't recognize generally trigger a search. To get around this web3 domains usually have a forward slash "/". For example ENS domains use a forward slash such as http://vitalik.eth/. Decentraweb domains function similarly with the added bonus that if you do want to host a website directly on the highest TLD-level you can by referencing the domain as "🐳./" for example. Generally, however just using "www.🐳/" is more user friendly than hosting direcly on a TLD.
