# Using IPNS + IPFS to distribute node updates?

**URL:** <https://discuss.ipfs.tech/t/using-ipns-ipfs-to-distribute-node-updates/15773>\
**Category:** Protocol\
**Created:** [December 31, 2022, 7:53pm UTC](https://discuss.ipfs.tech/t/using-ipns-ipfs-to-distribute-node-updates/15773 "2022-12-31T19:53:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![legowerewolf](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/legowerewolf/32/7307_2.png) [@legowerewolf](https://discuss.ipfs.tech/u/legowerewolf)\
**Post date:** [December 31, 2022, 7:53pm UTC](https://discuss.ipfs.tech/t/using-ipns-ipfs-to-distribute-node-updates/15773/1 "2022-12-31T19:53:32Z")

</div>

Basically what it says on the tin. Is there any reason why IPFS clients couldn’t keep themselves up to date by querying an IPNS name for new versions?

On the security side, I don’t think this would be much of an issue: the vast majority of us already trust the IPFS org on GitHub to distribute clean updates. Have it disabled by default and let people choose a different name to watch, and I think that problem would be solved.

---

<div class="post-metadata">

**Author:** ![Discordian](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/discordian/32/4692_2.png) [@Discordian](https://discuss.ipfs.tech/u/Discordian)\
**Post date:** [January 6, 2023, 7:43pm UTC](https://discuss.ipfs.tech/t/using-ipns-ipfs-to-distribute-node-updates/15773/2 "2023-01-06T19:43:44Z")

</div>

I suppose clients totally could, yeah. Kubo has [ipfs-update](https://github.com/ipfs/ipfs-update) too which can be quite handy. The binaries are already available over IPNS too as dist.ipfs.tech is a DNSLink address:

```auto
disco@MacBook-Air % ipfs name resolve /ipns/dist.ipfs.tech
/ipfs/QmNpLrDWJWsR6JeXy9KK1fU8DzYirLzqGgbhcAkvzqvyL3

```