** Summary changed:
- disable dnssec
+ Disable DNSSEC by default
** Changed in: systemd (Ubuntu)
Milestone: zesty-updates => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682499
Title:
D
This helped me only partially - I still have issues with DNS lookup.
It seems that the systemd-resolved is broken from the very idea.
After solving DNSSEC problem, I see now a switching problem - if one DNS
does not respond, resolved switches to another one, which may be a local
DNS not serving a
Installed 17.10 64bit development branch on a daily .iso @ 14/5/2017
problem is solved after editing: /etc/systemd/resolved.conf DNSSEC=off
and reboot
another duplicate:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1690605
--
You received this bug notification because you are a membe
This particular issue is now closed. Please open a new bug report
requesting a cherrypick.
We really should not use one bug report for all the past and future defects
:-)
We need a new bug number for SRU tracking purposes.
Regards,
Dimitri.
On 2 May 2017 5:01 pm, "allfox_wy" <1682...@bugs.laun
Greetings, everyone.
I'm on Ubuntu GNOME 17.04
I see that DNSSEC is now off by default, however, in my log, I would see
something like:
4 May 2 23:29:31 lavender systemd-resolved[1129]: Grace period over,
resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 10.2.5.7.
5 May 2
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by defa
On 20 Apr 2017 22:20, "Sean Dague" wrote:
For what it's worth, I reported a related issue up to the systemd-devel
mailing list, and it looks like in systemd 233 (the next version) things
work much better with DNSSEC. https://lists.freedesktop.org/archives
/systemd-devel/2017-April/038698.html
I
For what it's worth, I reported a related issue up to the systemd-devel
mailing list, and it looks like in systemd 233 (the next version) things
work much better with DNSSEC. https://lists.freedesktop.org/archives
/systemd-devel/2017-April/038698.html
I rebuilt the 233 out of debian experimental,
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by defa
Bug #1650877 and the others linked there (see comment #7) appear to be
duplicates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682499
Title:
disable dnssec
To manage notifications about this bug
@duggalsudeep
This is not a regression, we are intentionally disabling DNSSEC by
default; and yes you do need to change /etc/systemd/resolved.conf to
enable DNSSEC - just like in yakkety. It was a mistake that we enabled
it for zesty.
--
You received this bug notification because you are a membe
Regression Confirmed: Setting DNSSEC=yes in /etc/systemd/resolved.conf
after 232-21ubuntu3 update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682499
Title:
disable dnssec
To manage notifications
systemd version 232-21ubuntu3: verified OK.
How do I correctly enable DNSSEC as default ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682499
Title:
disable dnssec
To manage notifications about
systemd version 232-21ubuntu3: verified OK.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682499
Title:
disable dnssec
To man
Hello Dimitri, or anyone else affected,
Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
** Description changed:
- because pitti says so
+ [Impact]
- cherrypick from debian
+ * dnssec functionality in systemd-resolved prevents network access in
+ certain intra and extra net cases, due to failure to correctly validate
+ dnssec entries. As a work-around we should disable dnssec by d
** Changed in: systemd (Ubuntu Zesty)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682499
Title:
disable dnssec
To manage notifications about this bug go to:
http
** Changed in: systemd (Ubuntu Zesty)
Milestone: None => zesty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682499
Title:
disable dnssec
To manage notifications about this bug go to:
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/1682499
Title:
di
19 matches
Mail list logo
