Not the answer you're looking for? Browse other questions tagged docker docker-for-mac or ask your own question.
![Docker For Mac Renew Docker For Mac Renew](/uploads/1/2/5/3/125392845/720997410.jpg)
Expected behavior Docker for Mac uses resolv.conf for DNS resolution Actual behavior Docker for Mac uses something else for DNS resolution Information What mechanism does Docker for Mac use to resolve DNS? I am unable to log in to any private registries due to DNS issues, but the resolver shouldn't be used as I don't see it in resolv.conf or scutil. So that I can track down where the issue is, I need to understand how Docker for Mac resolves DNS.
I just had a similar issue to this after upgrading to latest Docker on 7th July 2017. We are using a private registry on our own network. /etc/resolv.conf and scutil -dns shows our two DNS nameservers and correct search domain but this seemed to be ignored by Docker.
I had manually added the DNS settings ('dns' and 'dns-search') in the Docker Preferences - Advanced tab a while ago so it seemed unrelated to Docker using the system DNS settings. I updated to the latest Docker 17.06.0-ce-mac19 (18663) today (17th July 2017) and it now works fine as before my previous upgrade. I'm not sure which version I was on before.