bobo89 Posted June 11, 2021 Share Posted June 11, 2021 (edited) I have a docker only vlan with no IPv4 assignment in the networking tab. On 6.8.3 all containers were happily accessing the right DNS server which is a pihole docker container. However after upgrading to 6.9.2 containers all have /etc/resolv.conf set to 127.0.0.11. Where was the change that is preventing the dockers from accessing the DNS as normal? Edited June 11, 2021 by bobo89 6.9.2 Quote Link to comment
Hank Moody Posted December 2, 2021 Share Posted December 2, 2021 Have you resorted this problem? I'm facing the same, already-running container with 127.0.0.11 do work, but generating the same instance with another IP get's 127.0.0.11 again but is unable to establish a DNS connection - pinging 8.8.8.8 works whereas google.com doesn't. Any help or clarification would be really appreciated! Kind regards Hank Quote Link to comment
bobo89 Posted December 2, 2021 Author Share Posted December 2, 2021 Have you resorted this problem? I'm facing the same, already-running container with 127.0.0.11 do work, but generating the same instance with another IP get's 127.0.0.11 again but is unable to establish a DNS connection - pinging 8.8.8.8 works whereas google.com doesn't. Any help or clarification would be really appreciated! Kind regards HankFrom memory this only affected some dockers. In the extra parameters field I added --dns DNS server Sent from my SM-G988W using Tapatalk 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.