# Ipfs name failing to resolve **URL:** \ **Category:** Uncategorized\ **Tags:** ipns\ **Created:** [November 28, 2017, 4:09pm UTC](https://discuss.ipfs.tech/t/ipfs-name-failing-to-resolve/1524 "2017-11-28T16:09:39Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![stebalien](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/stebalien/32/156_2.png) [@stebalien](https://discuss.ipfs.tech/u/stebalien)\ **Post date:** [November 29, 2017, 4:57am UTC](https://discuss.ipfs.tech/t/ipfs-name-failing-to-resolve/1524/5 "2017-11-29T04:57:58Z")
> [@Restaldt1](#): > > ^old id is still not resolving (probably working as intended) Yes. IPNS records expire every 24 hours (and are republished automatically every 12). If you stop publishing them (e.g., by not running a daemon or blowing away your local repo), they’ll disappear. See: > [@Confusion about IPNS](https://discuss.ipfs.tech/t/confusion-about-ipns/1414): > > I have read through the various docs and examples and am still confused a bit about IPNS. The use case I am using it for is pretty much standard I think: I want to publish a webapp and some assets on a private IPFS swarm. Other than using a private swarm, that is exactly the use case for which IPNS is introduced in the samples etc. However, I have had various problems with this. publishing and resolving was sometimes unbearably slow. publishing does not work at all if a node is not connected … --- _[View the full topic](https://discuss.ipfs.tech/t/ipfs-name-failing-to-resolve/1524)._