** 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 complaints about NXDOMAIN messages + logged by Ubuntu + + [regression potential] + + any regression would likely be isolated to systemd-resolved handling of + a NXDOMAIN response from its upstream nameserver, including possibly + failing to resolve a hostname or delays in resolving hostnames + + [scope] + + this is needed for all releases; the patch is not upstream, but carried + by Ubuntu + + [original description] + I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf - --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf + --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ - [connectivity] + [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. - Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" - => observe the NXDOMAIN noise over a couple few minutes - + => observe the NXDOMAIN noise over a couple few minutes + Now make the hostname absolute with the trailing dot above and run: - systemctl reload NetworkManager + systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" - => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes + => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it.
** Also affects: network-manager (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Hirsute) Importance: Medium Status: Fix Released ** Also affects: systemd (Ubuntu Hirsute) Importance: Wishlist Status: Triaged ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Groovy) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Hirsute) Status: Triaged => Fix Committed ** Changed in: systemd (Ubuntu Groovy) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Groovy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in network-manager source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in network-manager source package in Focal: Confirmed Status in network-manager source package in Groovy: New Status in systemd source package in Groovy: In Progress Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Committed Bug description: [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 complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope] this is needed for all releases; the patch is not upstream, but carried by Ubuntu [original description] I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp