# Use case for different IPNS Keys

**URL:** <https://discuss.ipfs.tech/t/use-case-for-different-ipns-keys/1600>\
**Category:** Help\
**Created:** [December 9, 2017, 5:22pm UTC](https://discuss.ipfs.tech/t/use-case-for-different-ipns-keys/1600 "2017-12-09T17:22:21Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![lidel](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/lidel/32/9853_2.png) [@lidel](https://discuss.ipfs.tech/u/lidel)\
**Post date:** [December 9, 2017, 6:59pm UTC](https://discuss.ipfs.tech/t/use-case-for-different-ipns-keys/1600/2 "2017-12-09T18:59:28Z")

</div>

You may want to be able to publish to the same IPNS address from different machines, each having its own IPFS node:

> [@Can multiple nodes share the same peer id?](https://discuss.ipfs.tech/t/can-multiple-nodes-share-the-same-peer-id/1204/3):
>
> Duplicate of node identity is probably a bad idea, but if you reframe the question into “can I publish to the same IPNS key from multiple boxes?”, then it makes more sense. If you use dedicated key for that. (Someone may want to publish a static blog from home, and then from work laptop) I created PoC of publishing to the same PeerId from two different boxes some time ago: [https://discuss.ipfs.tech/t/ipns-publishing-after-generating-a-key/90/4?u=lidel](https://discuss.ipfs.tech/t/ipns-publishing-after-generating-a-key/90/4)

---

_[View the full topic](https://discuss.ipfs.tech/t/use-case-for-different-ipns-keys/1600)._