Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Hirsute |
Fix Released
|
Medium
|
Unassigned | ||
systemd (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Bionic |
Fix Released
|
Medium
|
Dan Streetman | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Medium
|
Dan Streetman | ||
Hirsute |
Fix Released
|
Wishlist
|
Unassigned |
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/
--- /usr/lib/
+++ /usr/lib/
@@ -1,2 +1,2 @@
[connectivity]
-uri=http://
+uri=http://
Making this name absolute instead of relative avoids spurious resolutions of "connectivity-
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:/
Plenty of people annoyed by NXDOMAIN warnings, just Google it.
Changed in systemd (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → Medium |
Changed in network-manager (Ubuntu): | |
importance: | Undecided → Medium |
tags: | added: focal groovy |
tags: | added: rls-ff-incoming rls-gg-incoming |
Changed in network-manager (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in systemd (Ubuntu): | |
importance: | Medium → Wishlist |
Changed in systemd (Ubuntu): | |
importance: | Wishlist → Low |
Changed in systemd (Ubuntu): | |
importance: | Low → Wishlist |
description: | updated |
Changed in systemd (Ubuntu Hirsute): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Bionic): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Groovy): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Hirsute): | |
status: | Triaged → Fix Committed |
assignee: | Dan Streetman (ddstreet) → nobody |
Changed in systemd (Ubuntu Groovy): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Bionic): | |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Groovy): | |
importance: | Undecided → Medium |
no longer affects: | network-manager (Ubuntu Groovy) |
no longer affects: | network-manager (Ubuntu Focal) |
no longer affects: | network-manager (Ubuntu Bionic) |
Status changed to 'Confirmed' because the bug affects multiple users.