Closed Man-Jain closed 1 year ago
@Man-Jain are you failing to resolve on the same machine that published the record that works fine on ipfs.io, or a different one?
Yes, failing to resolve on the same machine from which the record was published. It's also not able to resolve any other IPNS record not published from that node.
There are two bugs here:
So I tested this behaviour (fetching my own record), I can see my own node is reaching out to the DHT which means at least self-caching is broken. However it loads for me (resolved with the DHT).
I will likely look (and possibly cleanup) boxo/namesys
when working on ipfs/boxo#329, so I can take this one.
I found out 3 bugs that prevents IPNS from working quickly right now. They make it always wait 1 minute before resolving any IPNS record, even if you get the first record in 10ms and DHT quorum in 200ms. https://filecoinproject.slack.com/archives/C04M8232QRW/p1688125350678669?thread_ts=1688118049.947789&cid=C04M8232QRW
The DHT quorum is between 200~400ms for me, this is the expected IPNS resolution speed and would be if we were not artificially slowing it down.
Triage notes:
2023-07-06 conversation: in addition to doing the fix and test, we need to create metrics and have it show up in Thunderdome. @lidel will create the followup issue for splitting out metrics between dnslink and ipns and making sure it shows up in Thunderdome.
Checklist
Installation method
ipfs-desktop
Version
Config
Description
I have an ipfs gateway running on a kuberentes, all ports exposed and appendAddress has the ip and random port(4001) of the ipfs gateway node, usePubsub is true and on running ipfs name resolve & through ipfs.io i’m able to resolve IPNS hash.
But I have not been able to resolve IPNS hash through the gateway on port 8080.
I keep getting the error could not resolve name.