-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
ipns publish: lower the default TTL #10718
Comments
What exactly do you mean by IPNS being slow in this context? Slow propagation of changes? or Slow to resolve? IIUC, you're referring to users that can't see their newly published IPNS record propagated, because nodes aren't looking up the new record due to the one hour TTL? |
Yes. In my subjective experience, virtually every "ipns is slow" argument I've heard in past 5 years ended up being TTL-related, upon closer inspection. TTL was set to default 1h, or raised to 24h, I've even seen someone setting validity and TTL to a year, and then complaining "IPNS is broken". All those issues went away when TTL was lowered. Filled related ipfs/ipfs-docs#2002 |
See rationale in ipfs/kubo#10718
Triage note:
|
chore(ipns): lower DefaultRecordTTL to 5m See rationale in ipfs/kubo#10718
Checklist
Description
Never-ending complains about IPNS being slow usually boil down to the implicit default of
--ttl
inipfs 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.
TODO
DefaultRecordTTL
to 5m boxo#859The text was updated successfully, but these errors were encountered: