Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Implement the jsipfs dns command #926

Closed
daviddias opened this issue Jul 23, 2017 · 1 comment
Closed

Implement the jsipfs dns command #926

daviddias opened this issue Jul 23, 2017 · 1 comment
Assignees
Labels
exp/expert Having worked on the specific codebase is important help wanted Seeking public contribution on this issue P3 Low: Not priority right now

Comments

@daviddias
Copy link
Member

Following: https://github.com/ipfs/js-ipfs/pull/925/files

We want to support the same command that go-ipfs supports: jsipfs dns.

From go-ipfs:

» ipfs dns --help
USAGE
  ipfs dns <domain-name> - Resolve DNS links.

SYNOPSIS
  ipfs dns [--recursive | -r] [--] <domain-name>

ARGUMENTS

  <domain-name> - The domain-name name to resolve.

OPTIONS

  -r, --recursive bool - Resolve until the result is not a DNS link. Default: false.

DESCRIPTION

  Multihashes are hard to remember, but domain names are usually easy to
  remember.  To create memorable aliases for multihashes, DNS TXT
  records can point to other DNS links, IPFS objects, IPNS keys, etc.
  This command resolves those links to the referenced object.

  For example, with this DNS TXT record:

        > dig +short TXT _dnslink.ipfs.io
        dnslink=/ipfs/QmRzTuh2Lpuz7Gr39stNr6mTFdqAghsZec1JoUnfySUzcy

  The resolver will give:

        > ipfs dns ipfs.io
        /ipfs/QmRzTuh2Lpuz7Gr39stNr6mTFdqAghsZec1JoUnfySUzcy

  The resolver can recursively resolve:

        > dig +short TXT recursive.ipfs.io
        dnslink=/ipns/ipfs.io
        > ipfs dns -r recursive.ipfs.io
        /ipfs/QmRzTuh2Lpuz7Gr39stNr6mTFdqAghsZec1JoUnfySUzcy
@daviddias daviddias added exp/expert Having worked on the specific codebase is important help wanted Seeking public contribution on this issue labels Jul 23, 2017
@daviddias daviddias added P3 Low: Not priority right now status/deferred Conscious decision to pause or backlog labels Jul 26, 2017
@daviddias daviddias added status/ready Ready to be worked and removed status/deferred Conscious decision to pause or backlog labels Sep 13, 2017
@daviddias
Copy link
Member Author

@hacdias shipped this one with #1172, thank you! ❤️

@ghost ghost removed the status/ready Ready to be worked label Feb 21, 2018
MicrowaveDev pushed a commit to galtproject/js-ipfs that referenced this issue May 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
exp/expert Having worked on the specific codebase is important help wanted Seeking public contribution on this issue P3 Low: Not priority right now
Projects
None yet
Development

No branches or pull requests

2 participants