Comment 3 for bug 1767900

@seb128 I'm in a Starbucks now. #1727237 does not fix my issue.

This seems to be a duplicate of open bug: #1766969 ( https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969 ), which forked from #1727237

**WORKAROUND:**

1. At Starbucks, connect to Google Starbucks WiFi.
2. Jump into a browser to have it identify a "server not found", need the name of the server in the browser address. (Example: Browser hangs on `https://aruba.odyssys.net`)
3. Open terminal and run `ip route` to determine ROUTER.IP (example: `ip route` returns `default via 172.31.98.1`)
4. Lookup the server IP address from local router by running `dig @ROUTER.IP server.not.found` (example: `dig @172.31.98.1 aruba.odyssys.net` returns `;; ANSWER SECTION:
aruba.odyssys.net. 0 IN A 172.31.98.1`)
5. Add IP address to /etc/hosts (Example: `sudo nano /etc/hosts` add the line: `172.31.98.1 aruba.odyssys.net`)
6. Add nameservers to /etc/resolv.conf (Example: `sudo nano /etc/resolv.conf` add lines above existing nameserver `nameserver 172.31.98.1` and `nameserver 8.8.8.8`)

Try again to connect (and don't reboot before connecting).

**Notes:**
After reviewing the output as I was sharing I realized
Step 4 might be totally unnecessary.
Step 5 is a permanent change that likely will affect your ability to connect at other Starbucks.
Step 6 is temporary and systemd will overwrite the file at reboot, possibly sooner.