# Dealing with "rapidly mutating" content on IPNS

**URL:** <https://discuss.ipfs.tech/t/dealing-with-rapidly-mutating-content-on-ipns/13093>\
**Category:** Help\
**Created:** [January 5, 2022, 6:16pm UTC](https://discuss.ipfs.tech/t/dealing-with-rapidly-mutating-content-on-ipns/13093 "2022-01-05T18:16:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![zacharywhitley](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/zacharywhitley/32/2670_2.png) [@zacharywhitley](https://discuss.ipfs.tech/u/zacharywhitley)\
**Post date:** [January 6, 2022, 12:44am UTC](https://discuss.ipfs.tech/t/dealing-with-rapidly-mutating-content-on-ipns/13093/2 "2022-01-06T00:44:49Z")

</div>

Take a looks at the —ttl and —lifetime flags for the ‘IPFS name publish’ command.

You might find this post helpful. [Clarification over TTL and LifeTime for IPNS Records - #2 by Magik6k](https://discuss.ipfs.tech/t/clarification-over-ttl-and-lifetime-for-ipns-records/4346/2)

---

_[View the full topic](https://discuss.ipfs.tech/t/dealing-with-rapidly-mutating-content-on-ipns/13093)._