[Touch-packages] [Bug 1862437] Re: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server

2020-02-20 Thread Bruce Goodman
** 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 Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1862437] Re: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server

2020-02-15 Thread Bruce Goodman
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

[Touch-packages] [Bug 1862437] Re: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server

2020-02-14 Thread Christian Ehrhardt 
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