hello in bionic
i also tried to get systemd.resolve and dnsmasq working
the /etc/default/lxc-net setup the dnsmasq using ultimately creating the
dnsmasq shown below
the config did assign static and dynamic ip's to the containers however i could
not access dynamic addresses by name. so i added to /etc/systemd/resolv.conf
attached below. that worked with the effect of the cpu utilization.
it seemed to jump up after i went to the net and was not accessing the
containers on 10.0.3.x as if systemd-resolve was sending queries to the
dnsmasq in a loop.. please look at global section has 10.0.3.1 as the
dns server and that doesn't look right. it is placed by
/etc/systemd/resolv.conf
ps ax:
dnsmasq --conf-file=/etc/lxc/dnsmasq.conf -s lxc -S /lxc/ -u lxc-dnsmasq
--strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid
--listen-address 10.0.3.1 --dhcp-range 10.0.3.128,10.0.3.254
--dhcp-lease-max=253 --dhcp-no-override --except-interface=lo
--interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases
--dhcp-authoritative
with :/etc/systemd/resolv.conf
[Resolve]
#DNS=
DNS=10.0.3.1
#FallbackDNS=
#Domains=
Domains=lxc
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#Cache=yes
i was also watching tcpdump on llxcbr0 which had no activity
after a while the systemd-resolve climbed approaching 100% with dnsmasq 50%
netstat -nlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
1643/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
1263/cupsd
tcp 0 0 10.0.3.1:53 0.0.0.0:* LISTEN
2518/dnsmasq
tcp6 0 0 :::22 :::* LISTEN
1643/sshd
tcp6 0 0 ::1:631 :::* LISTEN
1263/cupsd
udp 14592 0 0.0.0.0:5353 0.0.0.0:*
1399/avahi-daemon:
udp 0 0 0.0.0.0:22168 0.0.0.0:*
-
udp 0 0 0.0.0.0:6670 0.0.0.0:*
-
udp 0 0 0.0.0.0:56840 0.0.0.0:*
-
udp 0 0 0.0.0.0:62910 0.0.0.0:*
-
udp 0 0 0.0.0.0:48051 0.0.0.0:*
1399/avahi-daemon:
udp 13824 0 10.0.3.1:53 0.0.0.0:*
2518/dnsmasq
udp 9216 0 127.0.0.53:53 0.0.0.0:*
1007/systemd-resolv
udp 10240 0 0.0.0.0:67 0.0.0.0:*
2518/dnsmasq
udp 0 0 0.0.0.0:68 0.0.0.0:*
6025/dhclient
udp 0 0 0.0.0.0:631 0.0.0.0:*
1481/cups-browsed
udp6 4608 0 :::5353 :::*
1399/avahi-daemon:
udp6 0 0 :::59159 :::*
1399/avahi-daemon:
raw6 0 0 :::58 :::* 7
5918/NetworkManager
Active UNIX domain sockets (only servers)
/etc/resolv.conf: is under systemd link
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
search lxc
system-resolve --status:
Global
DNS Servers: 10.0.3.1
DNS Domain: lxc
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test
Link 4 (lxcbr0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 3 (wlp58s0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.1.1
2001:4888:47:ff00:406:d::
2001:4888:41:ff00:404:d::
Link 2 (eno1)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
i will continue to poke but ultimately don't wish to have fixed ip's
which must be in /etc/dnsmasq.d and in etc/hosts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1721092
Title:
systemd-resolved and dns-masq make CPU 100% when using lxc name
resolution
Status in systemd package in Ubuntu:
Triaged
Bug description:
This bug may be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364 but I'm
not sure, hence this new entry.
It hits while I wanted systemd to resolve the lxc domain to my
internal lxc hosts.
Step to (maybe) reproduce:
- having lxc installed
- make some user space lxc container
- uncomment the line LXC_DOMAIN="lxc" in /etc/default/lxc-net
- restart lxc-net service
Now the dnsmasq on 10.0.3.1 should be a dns resolving lxc names.
- add a file /etc/systemd/resolved.conf.d/lxc.conf
[Resolve]
DNS=10.0.3.1
Domains=~.lxc
DNSSEC=false
- restart systemd-resolved service
Now systemd knows it should ask .lxc names to dnsmasq
- start an lxc container, let assume it's called my-container
- ping it using my-container.lxc it should work
After some times, systemd-resolved should use 100% CPU.
Commenting the /etc/systemd/resolved.conf.d/lxc.conf file and
restarting it makes systemd-resolved never eating resources again.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-21ubuntu5
Uname: Linux 4.10.16-041016-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Oct 3 18:18:56 2017
InstallationDate: Installed on 2015-11-10 (692 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Intel Corporation Skylake Platform
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.16-041016-generic
root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash
crashkernel=384M-:128M vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to zesty on 2017-02-25 (219 days ago)
dmi.bios.date: 11/06/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: WhiteTip Mountain1 Fab2
dmi.board.vendor: Topstar
dmi.board.version: RVP7
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 9
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring:
dmi.product.name: Skylake Platform
dmi.product.version: 0.1
dmi.sys.vendor: Intel Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721092/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
