Checklist

• My issue is specific & actionable.
• I am not suggesting a protocol enhancement.
• I have searched on the issue tracker for my issue.

Description

Never-ending complains about IPNS being slow usually boil down to the implicit default of --ttl in ipfs name publish RPC being set to 1h.

It may not be the best default for Kubo and also not the best recommendation in Specs (https://specs.ipfs.tech/ipns/ipns-record/)

We may look into the default setting big DNS providers have (afaik Cloudflare uses 5 minutes for the same reason – a tradeoff between caching and user complaints due to slow propagation), and change spec recommendation and Kubo default to more pragmatic value.

Ref.

• https://discuss.ipfs.tech/t/ipns-best-setting-for-fast-update/18103/3?u=lidel
• https://discuss.ipfs.tech/t/ipfs-name-resolve-does-not-always-return-the-freshest-cid-for-ipns-on-kubo-0-20-0/16624/9?u=lidel

TODO

• ipns: lower the suggested default TTL specs#492
• chore(ipns): lower DefaultRecordTTL to 5m boxo#859