resolv.conf setting about docker-unbound HOT 8 CLOSED

The Container is just a Service as usual. so you have to set up clients to use unbound for name resolving

from docker-unbound.

understand Pat, however Service will pick up default resolver settings of the docker machine that is hosting it via Dhclient, thus any clients configured to use Service as their DNS will not be effected by the Unbound configuration that is listening on Interface 0.0.0.0. You need to set container's DNS resolver to also use localhost in order for it to process Client requests correctly. e.g.

currently: Client --> TCP/UDP 53 --> Docker Machine --> Container --> dhclient resolver (Unbound not processed)

suggest: Client --> TCP/UDP 53 --> Docker Machine --> Container --> localhost --> Unbound

Best, Fizz

from docker-unbound.

Still don't get it 100%. You are just talking about docker-machine, right? Because, for example, on a linux OS you can just deploy the container on :53 tcp/udp and can use 127.0.0.1 in resolv.conf.

BTW: Thanks for your interest 👍

from docker-unbound.

That's correct Pat - however if deployed within Amazon ECS, resolv.conf of the container is managed by Amazon EC2, thus you cannot just set to 127.0.0.1 as it gets overwritten by the VPC default DHCP settings. Thus using the docker --dns option resolves this constraint.

Great image by the way - working a treat!

from docker-unbound.

thanks for your explanation. I will add a section to the readme later 👍

from docker-unbound.

All good Pat.

Btw, would be nice to be able to access logs in future... i updated unbound.conf to use the file /usr/local/etc/unbound/unbound.log for logging; then added a RUN command into Dockerfile to create the initial file e.g. -

RUN touch /usr/local/etc/unbound/unbound.log

However using the docker run -v /logs:/usr/local/etc/unbound switch resulted in only the unbound.pid file being displayed in the Docker Host machine /logs directory. Not sure why the other files in the unbound container directory were not shown? Maybe it has to do with the permissions?

Rgds,

Ramon

From: Patrick Oberdorf <[email protected]mailto:[email protected]>
Reply-To: obi12341/docker-unbound <[email protected]mailto:[email protected]>
Date: Friday, 13 November 2015 at 11:13 PM
To: obi12341/docker-unbound <[email protected]mailto:[email protected]>
Cc: ramon <[email protected]mailto:[email protected]>
Subject: Re: [docker-unbound] resolv.conf setting (#1)

Closed #1#1 via 86b0b7chttps://github.com/obi12341/docker-unbound/commit/86b0b7c6a668c2a7fb8595a7994f556f519ac803.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#event-463532298.

from docker-unbound.

Hey,
no need to specify a log file. You can just use: -e VERBOSITY=5 and use docker logs -f unbound

from docker-unbound.

Cheers, will give it a try.

R

From: Patrick Oberdorf <[email protected]mailto:[email protected]>
Reply-To: obi12341/docker-unbound <[email protected]mailto:[email protected]>
Date: Friday, 13 November 2015 at 11:17 PM
To: obi12341/docker-unbound <[email protected]mailto:[email protected]>
Cc: ramon <[email protected]mailto:[email protected]>
Subject: Re: [docker-unbound] resolv.conf setting (#1)

Hey,
no need to specify a log file. You can just use: -e VERBOSITY=5 and use docker logs -f unbound

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-156416811.

from docker-unbound.