{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/20338","repository_url":"https://api.github.com/repos/docker/docker","labels_url":"https://api.github.com/repos/docker/docker/issues/20338/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/20338/comments","events_url":"https://api.github.com/repos/docker/docker/issues/20338/events","html_url":"https://github.com/docker/docker/issues/20338","id":133836366,"number":20338,"title":"run --dns regression in 1.10 with user networks","user":{"login":"jackstrain","id":3343836,"avatar_url":"https://avatars.githubusercontent.com/u/3343836?v=3","gravatar_id":"","url":"https://api.github.com/users/jackstrain","html_url":"https://github.com/jackstrain","followers_url":"https://api.github.com/users/jackstrain/followers","following_url":"https://api.github.com/users/jackstrain/following{/other_user}","gists_url":"https://api.github.com/users/jackstrain/gists{/gist_id}","starred_url":"https://api.github.com/users/jackstrain/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jackstrain/subscriptions","organizations_url":"https://api.github.com/users/jackstrain/orgs","repos_url":"https://api.github.com/users/jackstrain/repos","events_url":"https://api.github.com/users/jackstrain/events{/privacy}","received_events_url":"https://api.github.com/users/jackstrain/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-02-15T22:50:45Z","updated_at":"2016-02-15T23:07:51Z","closed_at":null,"body":"run --dns no longer works for user networks.\r\n\r\n`docker network create test`\r\n`docker run --dns=8.8.8.8 --net=test --rm ubuntu cat /etc/resolv.conf`\r\n\r\nPrints:\r\nnameserver 8.8.8.8 in 1.9\r\nnameserver 127.x.x.x in current 1.10.1 (not sure about earlier versions)\r\n\r\nEdit: This might just be how things are done now with the new dns based host resolution but I would just like to confirm. I need to prevent dns leaks in containers and without this option I will have to edit the resolv.conf every boot."},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/184434948","html_url":"https://github.com/docker/docker/issues/20338#issuecomment-184434948","issue_url":"https://api.github.com/repos/docker/docker/issues/20338","id":184434948,"user":{"login":"jackstrain","id":3343836,"avatar_url":"https://avatars.githubusercontent.com/u/3343836?v=3","gravatar_id":"","url":"https://api.github.com/users/jackstrain","html_url":"https://github.com/jackstrain","followers_url":"https://api.github.com/users/jackstrain/followers","following_url":"https://api.github.com/users/jackstrain/following{/other_user}","gists_url":"https://api.github.com/users/jackstrain/gists{/gist_id}","starred_url":"https://api.github.com/users/jackstrain/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jackstrain/subscriptions","organizations_url":"https://api.github.com/users/jackstrain/orgs","repos_url":"https://api.github.com/users/jackstrain/repos","events_url":"https://api.github.com/users/jackstrain/events{/privacy}","received_events_url":"https://api.github.com/users/jackstrain/received_events","type":"User","site_admin":false},"created_at":"2016-02-15T23:07:51Z","updated_at":"2016-02-15T23:07:51Z","body":"> Is there something in your use-case that no longer works in 1.10?\r\n\r\nYes I don't want to leak DNS requests on VPN containers.\r\n\r\nI'm guessing the DNS Server at 127.0.0.11 uses the hosts network stack to resolve the dns queries that don't match other containers?\r\n\r\nI'll remove the post tomorrow if noone has a good answer and this is really how things are supposed to be but atleast for my use case this is a regression."}}