.local Domains and WS1 UAGs

Annoyingly the Proton 3 OS doesn’t like .local style domain, if your organisation uses one you have 2 choices:

1. Create a new DNS zone and create new entries.
2. This simple hack.

NOTE: Initial testing looks successful, we ARE going to prod with this. But your mileage may vary. Haven’t experienced any issues with Workspace ONE Tunnel

So if you are deploying Unified Access Gateways (UAG’s) for Workspace ONE and are having issues with .local domain DNS resolution failing, this simple fix is for you.

1. Open nsswitch.conf for editing
2. Find the line “hosts: files resolve dns” and change it to “hosts: files dns resolve”
3. Save the file
4. Restart the systemd-resolve service

You should now be able to ping yourhost.local

We have our UAG’s deployed in Cascade mode, and only needed to do this on the backend UAG.