[tom@localhost ~]$ systemctl status systemd-networkd
● systemd-networkd.service - Network Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2015-05-01 15:45:57 HKT; 13s ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 281 (systemd-network)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-networkd.service
           └─281 /usr/lib/systemd/systemd-networkd

May 01 15:45:57 localhost systemd[1]: Starting Network Service...
May 01 15:45:57 localhost systemd-networkd[281]: Enumeration completed
May 01 15:45:57 localhost systemd-networkd[281]: eth0            : renamed to enp3s0
May 01 15:45:57 localhost systemd[1]: Started Network Service.
May 01 15:46:00 localhost systemd-networkd[281]: enp3s0          : gained carrier
May 01 15:46:00 localhost systemd-networkd[281]: enp3s0          : DHCPv4 address 192.168.11.3/24 via 192.168.11.1
May 01 15:46:00 localhost systemd-networkd[281]: enp3s0          : link configured
[tom@localhost ~]$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2015-05-01 15:45:57 HKT; 16s ago
     Docs: man:systemd-resolved.service(8)
 Main PID: 283 (systemd-resolve)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-resolved.service
           └─283 /usr/lib/systemd/systemd-resolved

May 01 15:45:57 localhost systemd[1]: Starting Network Name Resolution...
May 01 15:45:57 localhost systemd-resolved[283]: Using system hostname 'localhost'.
May 01 15:45:57 localhost systemd[1]: Started Network Name Resolution.
[tom@localhost ~]$ cat /etc/resolv.conf 
# This file is managed by systemd-resolved(8). Do not edit.
#
# Third party programs must not access this file directly, but
# only through the symlink at /etc/resolv.conf. To manage
# resolv.conf(5) in a different way, replace the symlink by a
# static file or a different symlink.

nameserver 192.168.11.1
[tom@localhost ~]$ systemctl suspend
[tom@localhost ~]$ cat /etc/resolv.conf 
# This file is managed by systemd-resolved(8). Do not edit.
#
# Third party programs must not access this file directly, but
# only through the symlink at /etc/resolv.conf. To manage
# resolv.conf(5) in a different way, replace the symlink by a
# static file or a different symlink.

nameserver 8.8.4.4
nameserver 2001:4860:4860::8844
nameserver 8.8.8.8
# Too many DNS servers configured, the following entries may be ignored.
nameserver 2001:4860:4860::8888
[tom@localhost ~]$ systemctl status systemd-networkd
● systemd-networkd.service - Network Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2015-05-01 15:45:57 HKT; 56s ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 281 (systemd-network)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-networkd.service
           └─281 /usr/lib/systemd/systemd-networkd

May 01 15:45:57 localhost systemd-networkd[281]: Enumeration completed
May 01 15:45:57 localhost systemd-networkd[281]: eth0            : renamed to enp3s0
May 01 15:45:57 localhost systemd[1]: Started Network Service.
May 01 15:46:00 localhost systemd-networkd[281]: enp3s0          : gained carrier
May 01 15:46:00 localhost systemd-networkd[281]: enp3s0          : DHCPv4 address 192.168.11.3/24 via 192.168.11.1
May 01 15:46:00 localhost systemd-networkd[281]: enp3s0          : link configured
May 01 15:46:43 localhost systemd-networkd[281]: enp3s0          : lost carrier
May 01 15:46:43 localhost systemd-networkd[281]: enp3s0          : DHCP lease lost
May 01 15:46:44 localhost systemd-networkd[281]: enp3s0          : gained carrier
May 01 15:46:44 localhost systemd-networkd[281]: enp3s0          : DHCPv4 address 192.168.11.3/24 via 192.168.11.1
[tom@localhost ~]$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2015-05-01 15:45:57 HKT; 1min 0s ago
     Docs: man:systemd-resolved.service(8)
 Main PID: 283 (systemd-resolve)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-resolved.service
           └─283 /usr/lib/systemd/systemd-resolved

May 01 15:45:57 localhost systemd[1]: Starting Network Name Resolution...
May 01 15:45:57 localhost systemd-resolved[283]: Using system hostname 'localhost'.
May 01 15:45:57 localhost systemd[1]: Started Network Name Resolution.
[tom@localhost ~]$ sudo systemctl restart systemd-resolved
[tom@localhost ~]$ cat /etc/resolv.conf 
# This file is managed by systemd-resolved(8). Do not edit.
#
# Third party programs must not access this file directly, but
# only through the symlink at /etc/resolv.conf. To manage
# resolv.conf(5) in a different way, replace the symlink by a
# static file or a different symlink.

nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844
nameserver 8.8.8.8
# Too many DNS servers configured, the following entries may be ignored.
nameserver 8.8.4.4
[tom@localhost ~]$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2015-05-01 15:47:08 HKT; 7s ago
     Docs: man:systemd-resolved.service(8)
 Main PID: 537 (systemd-resolve)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-resolved.service
           └─537 /usr/lib/systemd/systemd-resolved

May 01 15:47:08 localhost systemd[1]: Starting Network Name Resolution...
May 01 15:47:08 localhost systemd-resolved[537]: Using system hostname 'localhost'.
May 01 15:47:08 localhost systemd[1]: Started Network Name Resolution.
[tom@localhost ~]$ sudo systemctl restart systemd-networkd
[tom@localhost ~]$ cat /etc/resolv.conf 
# This file is managed by systemd-resolved(8). Do not edit.
#
# Third party programs must not access this file directly, but
# only through the symlink at /etc/resolv.conf. To manage
# resolv.conf(5) in a different way, replace the symlink by a
# static file or a different symlink.

nameserver 192.168.11.1
[tom@localhost ~]$ systemctl status systemd-networkd
● systemd-networkd.service - Network Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2015-05-01 15:47:29 HKT; 5s ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 548 (systemd-network)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-networkd.service
           └─548 /usr/lib/systemd/systemd-networkd

May 01 15:47:29 localhost systemd[1]: Starting Network Service...
May 01 15:47:29 localhost systemd-networkd[548]: Enumeration completed
May 01 15:47:29 localhost systemd[1]: Started Network Service.
May 01 15:47:29 localhost systemd-networkd[548]: lo              : link configured
May 01 15:47:29 localhost systemd-networkd[548]: enp3s0          : DHCPv4 address 192.168.11.3/24 via 192.168.11.1
May 01 15:47:29 localhost systemd-networkd[548]: enp3s0          : link configured
[tom@localhost ~]$