Comment 7 for bug 1766969

Revision history for this message
Mark Schroeder (earth2mark-eeepc) wrote : Re: DNS cannot be resolved in Hotel Hotspot

I have the latest systemd recommended by #1727237, and this issue still occurs at Starbucks as well. The Starbucks WIFI defect is #1767900 which appears to be a duplicate of this one.

ii systemd 237-3ubuntu10 amd64 system and service manager

I'm in a Starbucks now. #1727237 (the systemd above) does not fix my issue. aruba.odyssys.net is still not resolved using the stub-resolv.conf file (linked from /etc/resolv.conf).

cd /etc
sudo /bin/rm resolv.conf
sudo /bin/ln -s ../run/systemd/resolve/resolv.conf resolv.conf

Using the original resolv.conf however, as per the changes above, does work. I did not make any changes to /etc/hosts. The real resolv.conf above contains the google nameservers and is sufficient to resolve aruba.odyssys.net.

nameserver 8.8.8.8
nameserver 8.8.4.4
search home