> 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 message every 5
minutes to a few messages _per day_ (NM's default interval is 300
seconds)

The "journalctl --boot -p notice" total also becomes about twice
smaller. I filed this bug for a reason.


> the NXDOMAIN returned by the upstream nameserver is the *correct* response - 
> that hostname connectivity-check.ubuntu.com.your_domain really, actually 
> doesn't exist.

Yes of course, hence this one character fix which IMHO also removes one
large "distraction" from the main, captive portal issue!


> if you see this NXDOMAIN "error" [outside a captive portal] it is almost 
> always just a normal lookup of a domain that doesn't exist,

... which is for sure very rare on my (admittedly headless) system. Not
sure why querying inexistent domains would be frequent on others'
systems?

> and the error message is simply wrong

It says "mitigating _potential_..." so it's not strictly speaking wrong.
Agreed it can be misleading but summarizing this fairly complex issue in
just one line is quite a challenge.


> This is due to a Ubuntu-only patch to systemd 

Care to share the "best" link(s) about this? I mean links to best bugs
and/or relevant source code. An internet search returns too many hits!
BTW a good and authoritative bug number in the error message would
probably not hurt either, see why above.


> network-manager could work around this problematic Ubuntu-only systemd patch,

With an Ubuntu-only network-manager patch maybe? Sorry couldn't resist
:-)

-- 
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
  reduce NXDOMAIN warning noise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to