I found that in the 17.04 server edition it's enough to: $ sudo apt-get install dnsmasq $ sudoedit /etc/dnsmasq.d-available/lxc
add the following lines: server=/lxc/10.0.3.1 server=/3.0.10.in-addr.arpa/10.0.3.1 $ sudoedit /etc/default/lxc-net uncomment LXC_DOMAIN="lxc" But, in the desktop version, systemd-resolved and dnsmasq eat my cpu. Maybe a network-manager bug? 2017-03-29 1:25 GMT-03:00 Serge E. Hallyn <[email protected]>: > On Wed, Mar 29, 2017 at 12:59:15AM -0300, Norberto Bensa wrote: >> 2017-03-29 0:29 GMT-03:00 Serge E. Hallyn <[email protected]>: >> > On Wed, Mar 29, 2017 at 12:16:29AM -0300, Norberto Bensa wrote: >> >> Hello list! >> >> >> >> In previous versions of Ubuntu I had lxc domain name resolution >> >> working, but it's broken for me in 17.04. >> > >> > https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-network >> >> As I said, worked flawlessly up to 16.10, broken with 17.04. > > Ok, wasn't quite sure if you were following that recipe or not. > I wouldn't be surprised if the switch to systemd-networkd requires > a change. Personaly I'm on 16.04+upstart, but if you can come up with > the revised recipe an update to the serverguide would be awesome. > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
