Communicating with other sites when using Valet local DNSMasq with Porter

[Keoghan]

Typically DNSmasq will resolve the .test domain to 127.0.0.1. With docker, this is a problem for us, as in a container, this resolves to itself.

To allow us to communicate effectively, we need to use an alternative IP. Porter has a command to set up the host to listen on 10.200.10.1 - but it does not set up all the rest of the system for this, and the command will need to be run each time the machine is booted porter dns:set-host.

We will need to do a few things to work together with Valet in this situation.

• Adjust DNSmasq settings to point to 10.200.10.1 in ~/config/valet/dnsmasq.d/tld-test.conf replace 127.0.0.1 with 10.200.10.1
• Remove 127.0.0.1: from all the listen 127.0.0.1: parts nginx.conf files in ~/config/valet/Nginx so nginx will listen on all IPs for the machine. (Alternatively swap to use the new IP instead)
• Change 127.0.0.1 in /etc/resolver/test to 10.200.10.1
• Add 10.200.10.1 as the first DNS server in your network configuration
• valet restart

[Keoghan]

After @mikaelpopowicz PR's support for loopback to Laravel Valet, this is much easier now. laravel/valet#1039 available as of version 2.14.0

Now just run valet loopback 10.200.10.1 to achieve all the above, and benefit from Valet setting up a plist entry to ensure the loopback is set up each time your computer is started.