This bug was fixed in the package systemd - 237-3ubuntu10.45
---
systemd (237-3ubuntu10.45) bionic; urgency=medium
[ Ioanna Alifieraki ]
*
d/p/lp1911187-systemctl-do-not-shutdown-immediately-on-scheduled-shutdo.patch:
Do not shutdown immediately when scheduled shutdown fails
This bug was fixed in the package systemd - 245.4-4ubuntu3.5
---
systemd (245.4-4ubuntu3.5) focal; urgency=medium
[ Ioanna Alifieraki ]
*
d/p/lp1911187-systemctl-do-not-shutdown-immediately-on-scheduled-shutdo.patch:
Do not shutdown immediately when scheduled shutdown fails
This bug was fixed in the package systemd - 246.6-1ubuntu1.2
---
systemd (246.6-1ubuntu1.2) groovy; urgency=medium
[ Ioanna Alifieraki ]
*
d/p/lp1911187-systemctl-do-not-shutdown-immediately-on-scheduled-shutdo.patch:
Do not shutdown immediately when scheduled shutdown fails
root@lp1880258-b:~# dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.44 amd64system and service manager
root@lp1880258-b:~# host jifaslrjfiudrlj.com
Host jifaslrjfiudrlj.com not found: 3(NXDOMAIN)
root@lp1880258-b:~# journalctl -b -u systemd-resolved | grep NXDOMAIN
Mar 09
fixed in hirsute with:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=299002546ec2d62e7f0dd7d614ba958fc9df83c2
at version 247.3-1ubuntu4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
root@lp1880258-f:~# dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.4 amd64system and service manager
root@lp1880258-f:~# host gfjrisldfjrfj.com
Host gfjrisldfjrfj.com not found: 3(NXDOMAIN)
root@lp1880258-f:~# journalctl -b -u systemd-resolved | grep NXDOMAIN
Mar 09
with -release version of systemd:
root@lp1880258-g:~# host afhjisrfljsdirfj.com
Host afhjisrfljsdirfj.com not found: 3(NXDOMAIN)
root@lp1880258-g:~# journalctl -b -u systemd-resolved --no-pager
...
Mar 09 18:07:46 lp1880258-g systemd-resolved[624]: Server returned error
NXDOMAIN, mitigating
** No longer affects: network-manager (Ubuntu Groovy)
** No longer affects: network-manager (Ubuntu Focal)
** No longer affects: network-manager (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello MarcH, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello MarcH, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello MarcH, or anyone else affected,
Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [impact]
+
+ systemd-resolved emits a disturbingly large amount of NXDOMAIN log
+ messages that do not actually indicate any real problem
+
+ [test case]
+
+ see original description, or look at any log from any recent Ubuntu
+ system, or search google for endless
I just upgraded two machines to Ubuntu 20.04 LTS and /var/log/syslog is
full of:
systemd-resolved[...]: Server returned error NXDOMAIN, mitigating
potential DNS violation DVE-2018-0001, retrying transaction with reduced
feature level UDP.
with the only thing reported by tcpdump(8) as:
[...]
I ran tcpdump 'host ubuntu20 and port domain' on my router and looked at
all the other NXDOMAIN at boot time besides this one.
1. PTR request on the IPv4 address of my virbr0 interface. Gone after
uninstalling a couple libvirt-* packages
2. PTR request on ONE of my IPv6 addresses. It's not
> the vast, VAST majority of the time you see this message it is
actually not a NXDOMAIN error.
I don't have any extensive data as you seem to have but _for me at home_
(= office now!) and without zero captive portal involved, adding this
trailing dot reduces the NXDOMAIN frequency from one
> One thing that would help with these confusing NXDOMAIN errors in
general
the vast, VAST majority of the time you see this message it is actually
not a NXDOMAIN error. This is due to a Ubuntu-only patch to systemd to
work around some select captive portals that are slightly broken, so in
any
We discussed it in our meeting, it probably makes sense to include it in
the next SRU we do but we don't believe it deserves rls tracking,
updating the tag according to that decision
** Tags removed: rls-ff-incoming
** Tags added: rls-ff-notfixing
--
You received this bug notification because
> systemd behaviour could be better for domains without '.'
One thing that would help with these confusing NXDOMAIN errors in
general (not just from NetworkManager) is for systemd to provide a more
verbose and possibly less "private"[*] mode that shows the requested
domains somewhere without
@ Seb
systemd behaviour could be better for domains without '.'
however, that is considered low, in the light of network-manager fix.
Imho network-manager fix should be SRUed, do you agree? And it would be
on the desktop team to do so, right?
** Also affects: network-manager (Ubuntu Focal)
** Changed in: systemd (Ubuntu)
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880258
Title:
Add trailing dot to make connectivity-check.ubuntu.com. absolute and
** Changed in: systemd (Ubuntu)
Importance: Wishlist => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880258
Title:
Add trailing dot to make connectivity-check.ubuntu.com. absolute and
** Changed in: systemd (Ubuntu)
Importance: Low => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880258
Title:
Add trailing dot to make connectivity-check.ubuntu.com. absolute and
This bug was fixed in the package network-manager - 1.24.2-1ubuntu2
---
network-manager (1.24.2-1ubuntu2) groovy; urgency=medium
* debian/20-connectivity-ubuntu.conf: Add trailing dot to make
connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN
warning noise, thanks
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880258
Title:
Add trailing dot to make
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
** Tags added: focal groovy
** Tags added: rls-ff-incoming rls-gg-incoming
--
You
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/1880258
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (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/1880258
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880258
Title:
Add trailing dot to make
28 matches
Mail list logo
