Disable Landrush DNS Resolver in Parallels

[craigpearson]

Issue this fixes

Specific to the following configuration:

• HEAD Trellis
• Parallels as a provisioner
• Multisite subdomains enabled and Landrush used as DNS resolver

Without this change, when provisioning the above this will fail. Due to the attempt of Landrush attempting to being the DNS resolver for guest. For more information: https://discourse.roots.io/t/no-dns-resolution-in-development-vm-vagrant-parallels-multisite-landrush/23170

Specifically Landrush will attempt to change IP Tables and internal DNS on the vagrant machine, upon attempting this communication to services such as APT and any outside connections will fail. This is due to Parallels differing in network adapters created. Parallels by default wlll configure a shared adapter for NAT / DNS resolution. And a secondary adapter for the custom IP we specify. Landrush not knowing that DNS is handled that way will therefore break DNS/NAT.

Credit to this fix is all on @Twansparant

The current addition adds a conditional to Parallels provisioner, however if double nested if statements are okay, we could move this up to the block below, and instead check if the current provisioner is Parallels and prefer Landrush config grouping:

trellis/Vagrantfile

Lines 60 to 62 in e9e7c37

	config.landrush.enabled = true
	config.landrush.tld = trellis_config.site_hosts_canonical.reject { |host| host.end_with?(".#{main_hostname}") }
	hostnames.each { |host| config.landrush.host host, vconfig.fetch('vagrant_ip') }

[swalkinshaw]

Great debugging 🚀 I can't really test this myself so I'll trust it works based on the Discourse thread 😄