Hi,
In order to make IPFS/IPNS usefull and reliable, you have to consider how big and consistent your IPFS node swarm is. Every P2P distributed information system is depending on https://en.wikipedia.org/wiki/CAP_theorem
So, if you publish in the public IPFS network you try to reach from ipfs.io the DHT are too big to be able to keep consistency up there. So you have to “shape your swarm” and accelerate IPNS replication.
If your data have a slow mutable pace, you can use DNS Link technic to maintain accessibility
If your IPNS mutability have to be quick, this are ways to “make it work”:
-
Using IPFS cluster, but all of your nodes needs to be “equal”
-
Activate pub-sub to spread IPNS. To do so, activate the option:
ipfs config Pubsub.Router gossipsub- launch ipfs daemon with these features
--enable-pubsub-experiment --enable-namesys-pubsub
Then control your swarm… Manually using bootstap nodes of your own and even swarm.key encryption.
If your intention is to make it fully automatic. You have to couple your swarm with a “social/trust” communication system layer. I succeed using scuttlebutt a great “off grid” protocol: (2 years struggling with IPFS… And how I succeed using it with ScuttleButt! ).
Now I connect it to https://cesium.app wallets and https://gchange.fr
A great Libre currency experimentation network
So CAP Theorem is resolved by swarm control. You have to find the right way of doing it depending on your needs and application.