Systemd and a blocked/already in use port 53

[thinkst]

Systemd and a blocked/already in use port 53

Hey @nielsduelund,

I have actually hit into this issue too. Ill dig up the solution for you and let you know as soon as possible.

Hey @nielsduelund, @ndom91

Sorry for the delay. The workaround here is,

1. disable systemd-resolvd
2. remove the /etc/resolv.conf symlink (maybe back it up)
3. create new /etc/resolv.conf with contents pointing towards your favourite DNS. My /etc/resolv.conf has nameserver 8.8.8.8 in it.

Please let me know if you would like more of a description of the issue and how it is solved.

[nielsduelund]

Thanks for your reply. I may try it out at some tine, but for now I have swapped to using a Kali 18.04 instead of a lUbuntu 18.04. For some reason Kali works differently in this respect.
Please keep this thread for future reference for others. I have spent many hours of reinstalling because I thought i did something wrong.
Thanks for a great product :-)

[nielsduelund]

Hi
Finally I got to the point where I could test the work around, and YES it works !
Thanks a bunch :-)

[ndom91]

In the docker-compose.yml file I simply changed 53:53 to 54:53 so that it binds to port 54 on the outside and forwards it to 53 on the inside.

Im not using DNS Tokens so that was it for me. It was able to build then at least. In order ot get DNS Tokens to work again, that is another issue 😄

hey @nielsduelund,

Thats great 👍 Glad it is working.

[jayjb]

Closing issue because we found a good work around. Ill add the workout to the wiki for known issues with work arounds (when we get to that).