With --enable-pubsub-experiment --enable-namesys-pubsub enabled in IPFS 0.20.0, ipfs name resolve does not always return the most recent record I expect. However, if I add the -s option, it returns multiple results, one of which is the most recent one I was expecting. Currently, there seems to be no…

The difference you experience is likely due to the more modern IPNS implementation respecting TTL and doing a better job caching a valid IPNS resolution result for longer, and not hitting the network every time. Older Kubo/go-ipfs had hardcoded cache of 1m for /ipns/ids and that was all. It wasted …

`ipfs name resolve` does not always return the freshest CID for IPNS on Kubo 0.20.0

Help

livid June 14, 2024, 4:06am 8

On 0.29, an outdated result pops up from time to time.

Topic		Replies	Views
Kubo v0.29.0 is out! News go-ipfs , kubo	2	197	June 14, 2024
Unable to resolve IPNS name via remote IPFS nodes or public gateways (used to work fine) Help	15	531	March 13, 2024
IPNS Stopped Resolving Help ipns	10	571	June 13, 2023
Kubo versions > 0.15.0 gateway and slow IPNS performance Help go-ipfs , ipns , http-gateway	23	870	October 14, 2023
IPFS Kubo Gateway Using Gateway.NoFetch Breaks IPNS Resolution Kubo go-ipfs , ipns , gateway-ops , use-cases-and-apps	1	172	September 17, 2024

`ipfs name resolve` does not always return the freshest CID for IPNS on Kubo 0.20.0

Related topics