If you have a problem with the availability of port 53, because it is being used by another service, you may want to check out the following link:
github.com/dprandzioch/docker-ddns...
I found that directing traffic from 53 to 5353 worked, in which case you will have to start docker with something like this:
docker run -d --name coredns1 --restart=always --volume=/home/XXX/containers/coredns/:/root/ -p 5353:53/tcp -p 5353:53/udp coredns/coredns -conf /root/Corefile
This is covered in more detail in Aaron Hirsch's comment in the above link.
Thank you for this tutorial. Much appreciated!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If you have a problem with the availability of port 53, because it is being used by another service, you may want to check out the following link:
github.com/dprandzioch/docker-ddns...
I found that directing traffic from 53 to 5353 worked, in which case you will have to start docker with something like this:
docker run -d --name coredns1 --restart=always --volume=/home/XXX/containers/coredns/:/root/ -p 5353:53/tcp -p 5353:53/udp coredns/coredns -conf /root/Corefile
This is covered in more detail in Aaron Hirsch's comment in the above link.
Thank you for this tutorial. Much appreciated!