** Changed in: bind9 (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862437
Title:
Ubuntu 16.10
My sincere apologies, I have been wasting your time !
The Ubuntu and derivatives distributions that use systemd-resolved do
indeed query the assigned DNS. I verified this by stopping the
DNSMASQ service, which resulted in the loss of external name resolution.
Turning the service on again
We can see in your logs (thanks for all your effort BTW) that the failing cases
are exactly those which have:
...
Server: 127.0.0.53
Address: 127.0.0.53#53
...
That represents the switch to systemd-resolved.
It might be worth to check (and if you want report) your output of:
$ systemd-resolve
Apologies, I do not understand the interest in a vanilla lxc container.
My test distributions are all default bare metal installations in a
multi-boot configuration on a single ethernet connected laptop.
My appreciation of the Test Case code above is that it is doing an
nslookup on the host name
Thanks for the diagnostic command. It works ok in my local network,
could it be something to do with the way you're configuring your
hostname? Perhaps it would help if you could explain how you're
configuring your system, or show a test case that demonstrates the
problem in a vanilla lxc
** Description changed:
Starting Ubuntu 16.10 resolution of LAN addresses fails. This name
resolution failure is evident in every post 16.0 Ubuntu & derivative
that I have tested. See below - which shows 16.04 resolves, 18.04 and
Pop!_OS 19.04 fail, and other distros - Fedora 31,
I have been aware of this bug for some time, so in preparation for filing the
report I took a single laptop and did a default installation of each of the
below listed distributions, then added their initial updates, then tested.
On each distribution I ran this command;
hostnamectl | grep System
Thank you for taking the time to file a bug report. Since there isn't
enough information in your report to differentiate between a local
configuration problem and a bug in Ubuntu, I'm marking this bug as
Incomplete for the moment.
If indeed this is a local configuration problem, you can find
** Package changed: ubuntu => bind9 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862437
Title:
Ubuntu 16.10 & later, & derivatives do not query the assigned DNS
server
To manage
