# Synology DNS docker problem

**URL:** <https://forum.storj.io/t/synology-dns-docker-problem/12369>\
**Category:** troubleshooting\
**Tags:** docker, synology-nas\
**Created:** [March 21, 2021, 7:45pm UTC](https://forum.storj.io/t/synology-dns-docker-problem/12369 "2021-03-21T19:45:12Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![seanr22a](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/seanr22a/32/68_2.png) [@seanr22a](https://forum.storj.io/u/seanr22a)\
**Post date:** [March 21, 2021, 7:45pm UTC](https://forum.storj.io/t/synology-dns-docker-problem/12369/1 "2021-03-21T19:45:12Z")

</div>

I’ve been running storj since the beginning and everything has been working fine until now. I’m running storj on a Synology RS3618XS. I had a raid volume failure so I had to do a full reinstall but I can’t get storj running again. I followed the setup guide but in the final step using the long command it fails:

docker run -d --restart unless-stopped --stop-timeout 300   
-p 28967:28967   
-p 127.0.0.1:14002:14002   
-e WALLET=“0x65E0ac7bb7018b2114a958Fc40AE92193eD1f036”   
-e [EMAIL="myemail@hotmail.com](mailto:EMAIL=%22myemail@hotmail.com)"   
-e ADDRESS=“[myhost.dyndns.org:28967](http://myhost.dyndns.org:28967)”   
-e STORAGE=“18TB”   
–mount type=bind,source=/volume2/backup/storagenode,destination=/app/identity   
–mount type=bind,source=/volume2/storj,destination=/app/config   
–name storagenode storjlabs/storagenode:latest

The error I get is:  
2021-03-21T18:58:25.314009718Z 2021-03-21T18:58:25.313Z ERROR Invalid configuration. {“error”: “invalid contact.external-address: lookup “[myhost.dyndns.org](http://myhost.dyndns.org)” failed: lookup [myhost.dyndns.org](http://myhost.dyndns.org) on 1.1.1.1:53: read udp 172.17.0.2:58881-\>1.1.1.1:53: i/o timeout”, “errorVerbose”: “invalid contact.external-address: lookup “[myhost.dyndns.org](http://myhost.dyndns.org)” failed: lookup [myhost.dyndns.org](http://myhost.dyndns.org) on 1.1.1.1:53: read udp 172.17.0.2:58881-\>1.1.1.1:53: i/o timeout\n\[tstorj.io/storj/storagenode.(\*Config](http://tstorj.io/storj/storagenode.(*Config)).Ve rify:156\n\tmain.cmdRun:155\n\[tstorj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\n\tgithub.com/spf13/cobra.(\*Command](http://tstorj.io/private/process.cleanup.func1.4:363%5Cn%5Ctstorj.io/private/process.cleanup.func1:381%5Cn%5Ctgithub.com/spf13/cobra.(*Command)).execute:842\n\[tgithub.com/spf13/cobra.(\*Command](http://tgithub.com/spf13/cobra.(*Command)).ExecuteC:950\n\[tgithub.com/spf13/cobra.(\*C](http://tgithub.com/spf13/cobra.(*C) ommand).Execute:887\n\[tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.ExecCustomDebug:70\n\tmain.main:385\n\truntime.main:204](http://tstorj.io/private/process.ExecWithCustomConfig:88%5Cn%5Ctstorj.io/private/process.ExecCustomDebug:70%5Cn%5Ctmain.main:385%5Cn%5Ctruntime.main:204)”}

Doing a nslookup from the command line works fine for [myhost.dyndns.org](http://myhost.dyndns.org) (returns my external ip).

So I tried to enter my external ip directly in the startup command and got a little further but docker can’t lookup [tardigrade.io](http://tardigrade.io)

2021-03-21T19:18:47.191546217Z Error: trust: failed to fetch from source “[https://tardigrade.io/trusted-satellites](https://tardigrade.io/trusted-satellites)”: HTTP source: Get “[https://tardigrade.io/trusted-satellites](https://tardigrade.io/trusted-satellites)”: dial tcp: lookup [tardigrade.io](http://tardigrade.io) on 1.1.1.1:53: read udp 172.17.0.3:44965-\>1.1.1.1:53: i/o timeout

Something is wrong with name lookup from docker. It’s a plain new install with a untouched docker config. I’m running DSM 6.2.3-25426 Update 3. When I installed this the first time a long time ago there was a good synology specific install guide but it doesn’t seem to be available any longer.

Is there something I need to change in the Synology Docker config to make this work again ?

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [March 22, 2021, 5:50am UTC](https://forum.storj.io/t/synology-dns-docker-problem/12369/2 "2021-03-22T05:50:17Z")

</div>

There is no Synology-specific configuration. The network doesn’t work in your docker installation for some reason.  
Maybe you have some kind of firewall somewhere and it’s blocking traffic from your Synology.

---

<div class="post-metadata">

**Author:** ![seanr22a](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/seanr22a/32/68_2.png) [@seanr22a](https://forum.storj.io/u/seanr22a)\
**Post date:** [March 22, 2021, 7:39am UTC](https://forum.storj.io/t/synology-dns-docker-problem/12369/3 "2021-03-22T07:39:16Z")

</div>

We are not using the firewall in the Synology, it’s disabled. We have a lot of other applications running on this server and they are running fine. It’s only docker that has a problem. I got a support ticket with Synology now, we will see what they say.

---

<div class="post-metadata">

**Author:** ![Andrii](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/andrii/32/65_2.png) [@Andrii](https://forum.storj.io/u/Andrii)\
**Post date:** [March 22, 2021, 6:13pm UTC](https://forum.storj.io/t/synology-dns-docker-problem/12369/4 "2021-03-22T18:13:28Z")

</div>

Hmm, maybe problem just in misprint, you set -e ADDRESS:28967=[myhost.dyndns.org](http://myhost.dyndns.org) instead of  
-e ADDRESS=“[myhost.dyndns.org:28967](http://myhost.dyndns.org:28967)”

---

<div class="post-metadata">

**Author:** ![seanr22a](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/seanr22a/32/68_2.png) [@seanr22a](https://forum.storj.io/u/seanr22a)\
**Post date:** [March 22, 2021, 6:42pm UTC](https://forum.storj.io/t/synology-dns-docker-problem/12369/5 "2021-03-22T18:42:46Z")

</div>

It was a typo when I removed my real address 🙂 Thank you for notice - I’ve edited the original post now 👍

---

<div class="post-metadata">

**Author:** ![seanr22a](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/seanr22a/32/68_2.png) [@seanr22a](https://forum.storj.io/u/seanr22a)\
**Post date:** [March 22, 2021, 11:06pm UTC](https://forum.storj.io/t/synology-dns-docker-problem/12369/6 "2021-03-22T23:06:14Z")

</div>

Problem solved.

This server has multiple gateways and docker don’t like that for some reason … routing sorted out now and everything working.

Any chance to recover from this or is it just to start over again ?

 ![Untitled](https://storj-s3.bcdn.literatehosting.net/original/2X/9/96a4186d5859dcae0359ee8148cd8bae84636d7b.png)

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [March 23, 2021, 4:34am UTC](https://forum.storj.io/t/synology-dns-docker-problem/12369/7 "2021-03-23T04:34:40Z")

</div>

Just keep it online, it should recover in the next 30 days online.
