This seems to affect many public Wifi Hotspots. A very common example is
the new setup by Starbucks/Google (usually seen as **Google Starbucks
Wifi**) in the US by (Tech behind it is
with their

Under Ubuntu 16.04, Windows, Android, Mac OS, or iPhone, a WiFi guest
user can connect without problem.  However, since upgrading to Ubuntu
18.04, I've encountered this in at least three separate Starbucks stores
in Southern California.


An easier workaround, with fewer system modifications than the original
bug report is to use `ip route` to determine the IP address of the host
router, then add the hostname with that adress to `/etc/hosts`

Step by step details can be found here:

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.

  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:

Bug description:
  I was asked to create a new bug for this in as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to