hmmm... that's a bit tricky. What you're essentially running into is an updating problem. Your server needs to know how frequently it should be checking the network for updates. You can set the cache duration to be large, but then you may get a slow update. When you do a `pin` + NGINX update you are manually telling the server when to update and circumventing this problem.

In general, without doing some hacky stuff your laptop needs to be publishing the IPNS record at least daily or you may end up with some issues.

Note: As a cool thing you can use to get around this laptop republishing issue currently with IPNS over PubSub will keep around the most recent record and return it to you immediately. It'll need to find the record again every time you restart the daemon, but if you leave it on then this problem mostly disappears. However, you will need to change the lifetime of the IPNS record to be a long time so that the server doesn't consider it to be invalid (e.g. `ipns name publish --key myKey --lifetime 720h` to only have to republish once a month.