search

bioatlas / ala-docker

Dockerized version of Atlas of Living Australia components
GNU Affero General Public License v3.0
12 stars 12 forks source link

Troubles with name resolution when running ala-docker on networks that block certain DNS traffic... #26

Open mskyttner opened 6 years ago

mskyttner commented 6 years ago

If running on a corporate or guest network that is strict and blocks DNS traffic and forces usage of specific DNS servers, containers may not be able to reach out to the Internet using default settings.

A possible workaround could be to modify and hard-code settings for the local name resolution servers in the docker-compose.yml file within the dnsmasq section.

On some Linux OSes this command can be used to find the DNS servers in use:

nmcli dev show | grep DNS

SO post on finding what DNS servers are in use

for example the startup command for dnsmasq could be edited to use specific hard coded name DNS server to look like this assuming DNS ips in the corporate network are 130.238.96.1 and 130.238.98.11:

command: --log-facility=- --server=127.0.0.11 --server=130.238.96.1 --server=130.238.98.11 --server=193.10.57.11 --server=8.8.8.8 --server=172.16.0.72 --server=172.16.0.7 --neg-ttl=3600 --cache-size=1000 --max-cache-ttl=3600 --min-cache-ttl=3600 --all-servers

mskyttner commented 6 years ago

Suggestions for improvements and ideas for achieving a minimal config that mimics a production setup (with name resolution and SSL) on a development box are appreciated!