# IPNS publishing after generating a key

**URL:** <https://discuss.ipfs.tech/t/ipns-publishing-after-generating-a-key/90>\
**Category:** Help\
**Created:** [March 25, 2017, 8:16pm UTC](https://discuss.ipfs.tech/t/ipns-publishing-after-generating-a-key/90 "2017-03-25T20:16:58Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ralf](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@ralf](https://discuss.ipfs.tech/u/ralf)\
**Post date:** [March 27, 2017, 7:49am UTC](https://discuss.ipfs.tech/t/ipns-publishing-after-generating-a-key/90/5 "2017-03-27T07:49:39Z")

</div>

What I did was lookup if a key exists before generating: [IPFS Documentation | IPFS Docs](https://ipfs.io/docs/api/#apiv0keylist)  
But it’s true that I (re)generated the key at different nodes using the same input parameters.

So there’s only one way to publish at multiple nodes behind a load balancer at the moment:

- Manual copy of keystore file

It’s an easy job, but not when you run a lot of domains at the nodes. So it would be nice if sharing keystores could be automated.

- `key/pull?arg=<name>&peer=<peerid_of_node>`

Or send a custom peer id to the existing generate endpoint:

- `key/gen?arg=<name>&peer=<peerid_of_other_node>`

But that’s what you aswered here, right?

> Correct. Right now you can only publish to PeerID of your Identity key.  
> Support for publishing to alternative key is planned, but not implemented yet (v0.4.8-DEV):  
> .

---

_[View the full topic](https://discuss.ipfs.tech/t/ipns-publishing-after-generating-a-key/90)._