I have configure my network on "cheetahnew" with /etc/systemd/network/50-static.network rose@cheetahnew:/home/rose(5)$ cat /etc/systemd/network/50-static.network [Match] Name=eth0 [Network] DNS=141.89.64.1 DNS=141.89.194.254 Address=141.89.194.33/24 #Domains=bioinf.cs.uni-potsdam.de #[Address] #Address=141.89.194.33 #Broadcast=141.89.194.255 [Route] Gateway=141.89.194.254 "systemctl status systemd-networkd" does not show any error: rose@cheetahnew:/home/rose(6)$ systemctl status systemd-networkd ● systemd-networkd.service - Network Service Loaded: loaded (/usr/lib64/systemd/system/systemd-networkd.service; enabled) Active: active (running) since Di 2014-11-04 20:52:25 CET; 18h ago Docs: man:systemd-networkd.service(8) Main PID: 1950 (systemd-network) Status: "Processing requests..." CGroup: /system.slice/systemd-networkd.service └─1950 /usr/lib/systemd/systemd-networkd But /etc/resolf.conf is a link to an nonexisting file and nslookup does not resolve any dns names: rose@cheetahnew:/home/rose(7)$ ll /etc/resolv.conf lrwxrwxrwx 1 root root 32 24. Okt 14:59 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf rose@cheetahnew:/home/rose(8)$ nslookup distfiles.gentoo.org ;; connection timed out; no servers could be reached rose@cheetahnew:/home/rose(9)$ ll /run/systemd/resolve /bin/ls: Zugriff auf /run/systemd/resolve nicht möglich: Datei oder Verzeichnis nicht gefunden The directory /run/systemd/resolve does not exist. Restarting systemd-networkd.service does not help: root@cheetahnew:/root(10)# systemctl restart systemd-networkd.service root@cheetahnew:/root(11)# ll /etc/resolv.conf lrwxrwxrwx 1 root root 32 Oct 24 14:59 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf root@cheetahnew:/root(12)# ll /run/systemd/resolve /bin/ls: cannot access /run/systemd/resolve: No such file or directory
Please google the problem, or ask in a support forum before filing a bug. resolv.conf generation was moved to systemd-resolved in 215 or 216. systemctl enable systmed-resolved.service systemctl start systemd-resolved.service
(In reply to Mike Gilbert from comment #1) > Please google the problem, or ask in a support forum before filing a bug. > > resolv.conf generation was moved to systemd-resolved in 215 or 216. > > systemctl enable systmed-resolved.service > systemctl start systemd-resolved.service Thank you for your answer. But I was just googling few days ago and found the solution to run systemd-networkd and create manually the link from /run/systemd/resolve/resolv.conf to /etc/resolv.conf. But probably I still had an old version of systemd. Regards Juergen
