johnodon Posted July 3, 2017 Share Posted July 3, 2017 (edited) This was discussed in the pre-release subforum but things get lost quickly and easily so I am here to make an official request. Docker containers get their DNS server assignments from the host OS (unRAID). Now that v6.4 has the ability to assign static IPs to Docker containers, I would love to also be able to assign static DNS entries. Why you ask? Simple answer...DNS Leaks. I like to tunnel my Deluge and SAB containers trough my OPVN client (PIA) on my psfsense box via an Alias that is based on IP addresses. Right now I handle static IP and DNS (PIA's DNS servers) assignment to containers using the Pipework container. Sometimes my SAB and Deluge containers will not be reachable after an update and require a forced restart. They are the only 2 containers that have this issue so I think it has something to do with Pipework. I would like to retire the use of Pipework and assign static IP and DNS entries to these containers via the container configuration itself. John Edited July 3, 2017 by johnodon 1 Quote Link to comment
BRiT Posted July 3, 2017 Share Posted July 3, 2017 Have you tried using --dns and --dns-opt parameters in the advanced settings for each docker? Quote Link to comment
johnodon Posted July 3, 2017 Author Share Posted July 3, 2017 1 minute ago, BRiT said: Have you tried using --dns and --dns-opt parameters in the advanced settings for each docker? I can certainly try but would this work only with 6.4? I haven't moved from 6.3.5 yet. John Quote Link to comment
BRiT Posted July 3, 2017 Share Posted July 3, 2017 AFAIK, that option has been there since the very first unRaid docker implementation. I had to search through my posts from 2015 and the 6.0 beta series to remember what it was. Quote Link to comment
Lev Posted July 22, 2017 Share Posted July 22, 2017 Agree with OP, need more options for containers like DNS for the reasons he cited. Docker keeps improving on Unraid thanks I hear to bonienl hopefully this request will make the list. The 6.4-rc's are awesome, and this feature would be another step forward. Quote Link to comment
ijuarez Posted July 22, 2017 Share Posted July 22, 2017 On 07/03/2017 at 8:46 AM, johnodon said: This was discussed in the pre-release subforum but things get lost quickly and easily so I am here to make an official request. Docker containers get their DNS server assignments from the host OS (unRAID). Now that v6.4 has the ability to assign static IPs to Docker containers, I would love to also be able to assign static DNS entries. Why you ask? Simple answer...DNS Leaks. I like to tunnel my Deluge and SAB containers trough my OPVN client (PIA) on my psfsense box via an Alias that is based on IP addresses. Right now I handle static IP and DNS (PIA's DNS servers) assignment to containers using the Pipework container. Sometimes my SAB and Deluge containers will not be reachable after an update and require a forced restart. They are the only 2 containers that have this issue so I think it has something to do with Pipework. I would like to retire the use of Pipework and assign static IP and DNS entries to these containers via the container configuration itself. John Just wondering, have you tried using binhex delugevpn or his sabvpn and use the built in privoxy? 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.