*** This bug is a duplicate of bug 1727237 ***
https://bugs.launchpad.net/bugs/1727237
** This bug has been marked a duplicate of bug 1727237
systemd-resolved is not finding a domain
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
@Sebastien
Well, hmmm, it is possible that #1727237 is the same bug. The wifi I was using
at that time was a bit weird in regards of having a captive portal: It seemed
to me that it was implemented to show a captive portal in principle when
connecting to it. But while some other people around we
@Jan, were you maybe using a wifi behind a captive portal at the time?
could be bug #1727237 maybe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725680
Title:
DNS name resolution doesn't work on A
It seems Casper does not update /etc/systemd/resolved.conf
then I do not really know how you get this working if booting
from an untouched live 17.10 Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I was finally able to test, if I could reproduce the bug on a WPA2
encrypted private wifi network. And interestingly I couldn't - DNS
resolution worked fine when booting a live session and connecting to the
private network.
So it is possible that the behaviour I described in this report may be
som
I'm PXE booting 17.10 live with Serva.
I also found that the booting image DNS is broken.
I traced the problem to Casper within the booting initrd.lz, the file
/script/casper-bottom/23networking
does not populate
/etc/systemd/resolved.conf
therefore the DNS daemon does not work.
I've added to 23
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725680
Title:
DN
Yes, my wifi provides a DNS nameserver. It's adress is 192.168.44.1, and
it is shown when I open System Settings --> WLAN and click on the
properties of the connected network. When I manually add this DNS server
to resolv.conf, DNS resolution will start working.
What I'm currently using is some so
When you boot livecd and connect with network-manager to your wifi, what
is the output of:
$ systemd-resolve --status
$ sudo NetworkManager --print-config
Does your wifi provide DNS nameservers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I just tested that disabling systemd-resolved seems to be a good
permanent workaround for me (according to the description under
https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-
in-ubuntu )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
10 matches
Mail list logo
