search

sameersbn / docker-bind

Dockerize BIND DNS server with webmin for DNS administration
MIT License
913 stars 332 forks source link

Cannot access dns server after applying configs ";; connection timed out; no servers could be reached" #74

Closed snspinn closed 5 years ago

snspinn commented 5 years ago

I have been trying to configure the BIND container as a private network DNS server (loosely) following the DigitalOcean tutorial. I have been been getting the error ;; connection timed out; no servers could be reached once any configuration changes are applied.

As a debugging step I tried a "regular" install (service) of bind9. I am not getting the same issues if running a service (systemctl start bind9).

I think this is related to #65 i.e. as a result of running sudo systemctl stop systemd-resolved.service.

My docker-compose:

version: '2'

services:
  bind:
    image: sameersbn/bind:latest
    dns: 127.0.0.1
    ports:
    - 192.168.88.76:53:53/udp
    - 192.168.88.76:53:53/tcp
    environment:
    - WEBMIN_ENABLED=false
    volumes:
    - /srv/docker/bind:/data

Additional I am also seeing sudo: unable to resolve host ubuntu: Resource temporarily unavailable on the dns host when running the container.

pOH7 commented 5 years ago

My SOLUTION: udpate docker desktop to 2.1.0.1(37199)

snspinn commented 5 years ago

Thanks @pOH7 . I'll probably upgrade now though I got it working (and forgot to update this question) Do you find that the line dns: <some-ip> is necessary?

Changing this line to my local IP worked for me.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.