Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ipfs dns throws Error: could not resolve name (recursion limit exceeded) #6086

Closed
niinpatel opened this issue Mar 16, 2019 · 2 comments · Fixed by #6087
Closed

ipfs dns throws Error: could not resolve name (recursion limit exceeded) #6086

niinpatel opened this issue Mar 16, 2019 · 2 comments · Fixed by #6087
Assignees

Comments

@niinpatel
Copy link

niinpatel commented Mar 16, 2019

Version information:

go-ipfs version: 0.4.18-
Repo version: 7
System version: amd64/windows
Golang version: go1.11.1

Type: bug

Description:

run ipfs dns ipfs.io on the terminal

OR go to: https://ipfs.io/api/v0/dns?arg=ipfs.io

Both are showing the exact same error so I assume they're coming from the same place.

Expected behavior is that it should give an ipns path something like /ipns/website.ipfs.io

Stebalien added a commit that referenced this issue Mar 16, 2019
This is what users expect.

fixes #5635
fixes #5585
fixes #4181
fixes #4293
fixes #6086

License: MIT
Signed-off-by: Steven Allen <steven@stebalien.com>
@ghost ghost assigned Stebalien Mar 16, 2019
@ghost ghost added the status/in-progress In progress label Mar 16, 2019
@ghost ghost removed the status/in-progress In progress label Mar 19, 2019
@zicmama
Copy link

zicmama commented Apr 18, 2019

"ipfs name resolve" run into the same error
Error: could not resolve name (recursion limit exceeded)

The Site_ID is containing 1446 directories and 39254 sub CID in total...
Where is the limit?

It opens in web browser (DNSLink procedure) but every directory is 404.

@Stebalien
Copy link
Member

@zicmama please file a new issue (and include additional information like your IPFS version).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants