# Speeding up IPNS resolve time **URL:** \ **Category:** Kubo\ **Tags:** ipns\ **Created:** [January 12, 2018, 7:22pm UTC](https://discuss.ipfs.tech/t/speeding-up-ipns-resolve-time/1817 "2018-01-12T19:22:51Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![arby](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/arby/32/2435_2.png) [@arby](https://discuss.ipfs.tech/u/arby)\ **Post date:** [January 12, 2018, 7:22pm UTC](https://discuss.ipfs.tech/t/speeding-up-ipns-resolve-time/1817/1 "2018-01-12T19:22:51Z")
Are there any tricks to speed up the IPNS lookup time? It seems to take something like 5-10 seconds per request, where if I’m looking up a few published links it can take quite a while. ---
**Author:** ![leerspace](https://avatars.discourse-cdn.com/v4/letter/l/94ad74/32.png) [@leerspace](https://discuss.ipfs.tech/u/leerspace)\ **Post date:** [January 16, 2018, 12:44am UTC](https://discuss.ipfs.tech/t/speeding-up-ipns-resolve-time/1817/2 "2018-01-16T00:44:51Z")
I don’t think there are any major tricks right now. There’s at least one issue for this here: [https://github.com/ipfs/go-ipfs/issues/3860](https://github.com/ipfs/go-ipfs/issues/3860) The fact that [ipfs.io](http://ipfs.io) uses an `/ipfs/` dnslink record instead of an `/ipns/` one adds some weight to the assumption that there’s probably not currently a way to make IPNS lookups fast. My impression is that there are some significant changes planned for IPNS so this may change in the future. ---
**Author:** ![leerspace](https://avatars.discourse-cdn.com/v4/letter/l/94ad74/32.png) [@leerspace](https://discuss.ipfs.tech/u/leerspace)\ **Post date:** [April 3, 2018, 11:48pm UTC](https://discuss.ipfs.tech/t/speeding-up-ipns-resolve-time/1817/3 "2018-04-03T23:48:24Z")
As of v0.4.14, IPNS resolution is a lot faster now when using the new pubsub IPNS resolver and publisher: [https://ipfs.io/blog/34-go-ipfs-0.4.14#ipns-improvements](https://ipfs.io/blog/34-go-ipfs-0.4.14#ipns-improvements).