Brian Palmer

Oh you are too kind, thanks. If you (or anybody else) wants to take a stab at this, I think we'd basically need to iterate over all env vars with...

It should be possible -- you'd need to either specify all TLDs up front, or a more seamless approach would be to have code dynamically build up the list of...

Oh sorry, now that I think about it again, the second more automatic approach wouldn't work as I've described it. You'd also need something running on the host OS X...

The filename is significant -- `/etc/resolver/docker` tells OS X to use that config for DNS only for the `docker` TLD. To resolve `*.dev` you'd need an `/etc/resolver/dev` as well, for...

`Failure EADDRINUSE` sounds like another container is already listening on 443. Try shutting down that other container first, if you are using Dinghy then it could just be the built-in...

Hm, that sounds like Docker for Mac is not using the host DNS resolver. It seemed to be the last time I tried it, but that was a few months...

I've confirmed this doesn't work anymore with Docker for Mac version `1.12.0-a`. As far as I've been able to figure out, the VM is running its own DNS server and...

Another thing we could try is to actually modify the OS X DNS settings to add our resolver. If we do that, the DNS server that Docker for Mac is...

It looks like this is a known issue with Docker for Mac: https://forums.docker.com/t/docker-pull-not-using-correct-dns-server-when-private-registry-on-vpn/11117/8 They have a private bug tracker where this is assigned issue # 3124, but it doesn't sound...

Since the DNS resolver is running in a container in the VM, listening on port 19322, you should be able to just set the IP to 127.0.0.1 and configure to...