# Pin IPNS entries?

**URL:** <https://discuss.ipfs.tech/t/pin-ipns-entries/5290>\
**Category:** Help\
**Tags:** js-ipfs, go-ipfs, ipns, dht\
**Created:** [April 24, 2019, 5:48pm UTC](https://discuss.ipfs.tech/t/pin-ipns-entries/5290 "2019-04-24T17:48:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![leerspace](https://avatars.discourse-cdn.com/v4/letter/l/94ad74/32.png) [@leerspace](https://discuss.ipfs.tech/u/leerspace)\
**Post date:** [April 25, 2019, 1:29am UTC](https://discuss.ipfs.tech/t/pin-ipns-entries/5290/2 "2019-04-25T01:29:02Z")

</div>

> [@npfoss](#):
>
> Is it possible to pin IPNS entries so that your peers don’t have to wait forever for the DHT?

You mean like cache the entry? I think this already happens to some extent. It seems like the part that takes a long time is trying to find newer/better entries from the DHT.

There are already timeout parameter and DHT limit parameters that can cut down on how long IPNS resolution takes if you don’t care about having the newest value. To copy paste from a [different thread](https://discuss.ipfs.tech/t/reproviding-an-ipns-record-without-changing-it/5185/2), you can do a couple of things to speed up name resolution if you don’t care about the newest record.

```bash
# stream DHT entries as they're returned
ipfs name resolve --stream /ipns/...

# look for 2 records from the DHT to resolve the address, and only take up to 5 seconds
ipfs name resolve --dhtrc 2 --dhtt 5s /ipns/ 

```

---

_[View the full topic](https://discuss.ipfs.tech/t/pin-ipns-entries/5290)._
