Documentation
  • INTRODUCTION
    • What is ENS?
    • What is a dWebsite?
    • What is IPFS/IPNS?
    • What is eth.limo?
      • Gateway Basics
        • DNS over HTTPS
  • Beginner
    • How to register an ENS domain/name
    • Setting up a GitHub Repository
    • How To Install IPFS Locally
      • IPFS Desktop (Windows)
      • IPFS Desktop (Linux)
      • IPFS Desktop (Mac)
    • How to use IPFS/IPNS
      • Uploading to IPFS
        • Self-Hosting Instructions for IPFS and IPNS
        • Hosting using a pinning service
    • Setting Up Your ENS Name/Domain
      • Updating Your ENS Content Records
      • Content Hash Overview
        • Understanding Content Hashes, IPNS, and IPFS for ENS
        • Understanding IPFS Content Identifiers (CIDs)
  • IPFS Pinning Providers
    • Filebase
      • Using the Filebase Public IPFS Gateway
      • Filebase IPFS Pinning
  • STATIC SITE BUILDERS/TEMPLATES
    • -
  • Intermediate
    • Using eth.limo with IPFS (Kubo)
    • -
    • -
    • -
  • .ART Resolution
  • .gno Resolution
Powered by GitBook
On this page
  1. Intermediate

Using eth.limo with IPFS (Kubo)

Previous-Next-

Last updated 1 year ago

The most popular IPFS client, (formally go-ipfs) can be configured to use eth.limo DNS for native ENS resolution by running the following command:

$ ipfs config --json DNS.Resolvers '{"eth.": "https://dns.eth.limo/dns-query"}'

Verify that the changes have been saved:

$ cat ~/.ipfs/config | jq .DNS
{
  "Resolvers": {
    "eth.": "https://dns.eth.limo/dns-query"
  }
}

In order for the changes to take effect, you must restart the IPFS process.

ENS names must be prefixed with /ipns/ in order to successfully resolve them:

$ ipfs resolve -r /ipns/vitalik.eth
/ipfs/QmUWvM2pXSMk8kFMDqDnskMnURePtayXUECMYfwUJYgbks
Kubo