** Changed in: systemd
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow
** Changed in: nextcloud-snap
Status: Unknown => Fix Released
** Changed in: nextcloud-snap
Importance: High => Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
127.0.0.53 stub resolver was only introduced in v231, thus there is
nothing to fix in xenial.
** Changed in: systemd (Ubuntu Xenial)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
** Changed in: systemd (Ubuntu Xenial)
Milestone: ubuntu-16.04.3 => None
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53
This bug was fixed in the package systemd - 231-9ubuntu4
---
systemd (231-9ubuntu4) yakkety; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if
resolved is going to be started, make sure this blocks
network-online.target. LP: #1673860.
*
Ubuntu Core 16 also uses resolved, so this bug also needs to be fixed in
xenial.
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Xenial)
Status: New => Triaged
** Changed in: systemd (Ubuntu Xenial)
Milestone: None =>
Verified by way of a slightly modified test case:
- boot a yakkety cloud image
- verify 127.0.0.53 in /etc/resolv.conf
- sudo sed -i -e's/resolve \[[^]]*\] //' /etc/nsswitch.conf
- ping www.freedesktop.org -> FAIL
- install systemd from -proposed
- ping www.freedesktop.org -> SUCCESS
**
This bug report is about resolved not resolving CNAME records. If you
are seeing issues with resolved and DNSSEC, please follow LP: #1682499
instead.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
The same issue as Sudeep Duggal say (Ubuntu 17.04 bug, Ubuntu 16.10
works fine).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53
Anders, this commit was pushed to stretch but not to zesty:
https://anonscm.debian.org/git/pkg-
systemd/systemd.git/commit/?h=stretch=3361c8f55c
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Martin, was the DNSSEC=allow-downgrade default not switched off for the
17.04 stable release like you said it would?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Hello,
I did a clean install of the Ubuntu 17.04 release today. All websites
were opening correctly in Chrome/Firefox using on a LAN connection.
However, on WiFi, gmail/youtube are not opening in Chrome/Firefox. I am
able to successfully ping both gmail and youtube. Other websites
successfully
Hello Anders, or anyone else affected,
Accepted systemd into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/231-9ubuntu4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
And the problem is back in next reboot. Not sure what is happening here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53 server
Ah. Sorry. libnss-resolve was indeed the culprit. Removing it fixed the
issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53
I don't know if this is related but now it simply could not resolve
https://www.aviationweather.gov and www.noaa.gov. The result is the same
through ping and wget.
However when I try ip address of www.aviationweather.gov in browser it
works.
** Description changed:
+ [SRU Justification]
+ Ubuntu 16.10 server uses systemd-resolved by default, configured both as a
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved
talking to the dbus service. The DNS stub resolver has a bug that causes it to
fail to resolve
** Changed in: nextcloud-snap
Importance: Unknown => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not
Replying to #35:
> So, I'm downgrading this from critical to high since it only hits users of
> 16.10 server in a few corner cases (i.e. containers, chroots without
> libnss-resolve installed). It should still be SRUed.
Another corner case seems to be binaries linked against musl libc, since
** Bug watch added: github.com/nextcloud/nextcloud-snap/issues #178
https://github.com/nextcloud/nextcloud-snap/issues/178
** Also affects: nextcloud-snap via
https://github.com/nextcloud/nextcloud-snap/issues/178
Importance: Unknown
Status: Unknown
--
You received this bug
I was reminded that libnss-resolve is in 'standard' now, which means
it's also installed by default on server and any bugs that affect only
the stub DNS resolver without affecting the dbus service - such as this
one - do not impact DNS resolution by default on server in 16.10.
(I was wondering
As I recall resolved is also enabled by default in Ubuntu Server 16.10
(though not on Desktop), so this is a critical issue there as well.
Dimitri, could you please have a look at this backport?
Could someone who's seeing the DNSSEC problem please also file a
separate bug report, so we can track
Yes, there, see "man resolved.conf". But I'd recommend a separate file
to avoid changing the package-provided conffile:
sudo mkdir -p /etc/systemd/resolved.conf.d
printf "[Resolve]\nDNSSEC=no\n" | sudo tee
/etc/systemd/resolved.conf.d/no-dnssec.conf
--
You received this bug notification
#31, same problem also. As workaround for me - I just downgraded
network-manager package to 1.4.4-1ubuntu1 . Downloaded it from here -
https://launchpad.net/ubuntu/+source/network-manager/1.4.4-1ubuntu1/ and then
sudo dpkg -i network-manager_1.4.4-1ubuntu1_amd64.deb . And blocked this
version
Same problem as Fred here. It worked before the cherry-picking back
98974a88 and 47c16e59. But now it's broken. And yes everything works
with "DNSSEC supported: no".
@Martin
How do I disable DNSSEC? Through /etc/systemd/resolv.conf? And how to
switch it off "DNSSEC=allow-downgrade" ?
--
You
Note: We keep DNSSEC=allow-downgrade during development to collect
feedback, but switch it off for stable releases (we did so in yakkety
and should do so again in zesty). So if you have some trouble which is
DNSSEC related, it would be good to get a debug output of resolved while
it's failing to
I will say that I've noticed a delay in having the network come up too,
but that predates the new network-manage, and the latest systemd. It's
been going on for a while now but I haven't managed to report a bug on
it yet.
I have several startup apps configured in my Gnome environment,
including
So when I start my computer, then I cannot ping youtube.com, I start
Chromium, I still cannot ping youtube.com, then I open Firefox, and boom
magically everything worked! :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager
Was chatting then I noticed my DNS had suddenly started working normally
and YouTube resolved again.
I ran systemd-resolve --status
Under "Link 2 (eth0)" it said "DNSSEC supported: no".
I then restarted the computer, and now the DNS is broken again. It now
says "DNSSEC supported: yes".
Minutes
Steve, I am using 232-18ubuntu1.
$ dpkg -l | grep systemd
ii dbus-user-session 1.10.10-1ubuntu2
all simple interprocess messaging system (systemd --user
integration)
ii libnss-resolve:amd64 232-18ubuntu1
André, Fred, are you both definitely running the newest version of
systemd-resolved? You must be using the version from systemd
232-17ubuntu1, which just reached zesty yesterday. The resolved service
*should* be automatically restarted when you upgrade the package.
--
You received this bug
Interesting. It worked and works for me. I tested the version in my
PPA, both outside and inside a chroot (it was the inside-chroot that was
previously broken). I just dist-upgraded my other Zesty machine and
rebooted, and I am having no troubles resolving both IP and domain names
both on my
Barry, I think something went wrong. My DNS worked previously, but after
the update it resolves google.com but not many other domains such as
youtube.com. :(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
version 1.4.4-1ubuntu2 (from pre-release and from Barry's ppa) is not
working correctly for me
Can only ping any host by ip and never by hostname (google.com /
sapo.pt)
** Attachment added: "Selection_00553.png"
output of
$ systemd-resolve --status
** Attachment added: "Selection_00554.png"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647031/+attachment/4821012/+files/Selection_00554.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
I'll cherry pick back 98974a88 and 47c16359 now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow CNAME
This bug was fixed in the package systemd - 232-17ubuntu1
---
systemd (232-17ubuntu1) zesty; urgency=medium
* debian/patches/0001-resolved-follow-CNAMES-for-DNS-stub-
replies.patch: cherry-pick upstream fix for following CNAMEs in DNS
stub replies. Closes LP: #1647031.
Fixed upstream:
https://github.com/systemd/systemd/commit/e8d23f92b50a97bb3
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
This bug was fixed in the package network-manager - 1.4.2-3ubuntu2
---
network-manager (1.4.2-3ubuntu2) zesty; urgency=medium
* Revert 98974a88 and 47c16e59 (network-manager switching from dnsmasq
to resolved) because of bugs in resolved's resolution of CNAME
records. (LP:
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s
I've tested the PPA package and am satisfied that it restores CNAME
resolution in schroots without any observed regression otherwise. I
will upload it momentarily.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
I've uploaded a version with the reverts to my PPA:
https://launchpad.net/~barry/+archive/ubuntu/experimental
A local build looks promising, but I want to test it more before I
upload it for real. Please do test the PPA version once it builds.
--
You received this bug notification because you
As per pitti's email in #12, added network-manager bugtask and
subscribed pitti.
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Status:
43 matches
Mail list logo
