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 of the querying machine - it is resolving its
own name. The name resolution issue I'm trying to convey is that
Ubuntu 16.10 and forward, and derivative distributions, do not query
their assigned DNS to resolve host names of other devices on the LAN.
In the example I have used, BGOWIKI01v resides on another of my LAN's
computers. BGOWIKI01v has a static IP address asigned, as do several
other servers and printers I have, and their IP address to hostname
assignments are stored in the hosts file on my DNS server computer. So
when my machines need to resolve a nearby host name it queries the DNS,
which returns the address from its hosts file. That mechanism has been
shown in the extracts provided above to work for the other cited
distributions. Moreover, Windows (7 and 10) machines, tablets (both
IOS and Android), and Android phones that connect wirelessly also
resolve other host names on my LAN.
Put simply, except for Ubuntu 16.10 forward and derivatives, the
browsers on every other device on my LAN can resolve and load the wiki
pages hosted on my BGOWIKI01v virtual. Ubuntu 16.10 forward and
derivatives do not.
This additional snippet may help - these commands were run on the Ubuntu
18.04 MATE petition;
bruce@BGOLIN702:~$ nslookup BGOWIKI01v
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find BGOWIKI01v: SERVFAIL
bruce@BGOLIN702:~$ nslookup
> BGOWIKI01v
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find BGOWIKI01v: SERVFAIL
> server 192.168.3.2
Default server: 192.168.3.2
Address: 192.168.3.2#53
> BGOWIKI01v
Server: 192.168.3.2
Address: 192.168.3.2#53
Name: BGOWIKI01v
Address: 192.168.3.60
> ^Cbruce@BGOLIN702:~$ nslookup BGOWIKI01v
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find BGOWIKI01v: SERVFAIL
bruce@BGOLIN702:~
What this shows is name resolution fails, as I've described.
But when I enter into nslookup and manually assign the DNS server the lookup
succeeds.
However, on exit from nslookup resolution again fails.
Regards
Bruce Goodman
** Changed in: bind9 (Ubuntu)
Status: Incomplete => New
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1862437/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
