Ok, hier die Ergebnisse:
# resolvectl status
Global
LLMNR setting: yes
MulticastDNS setting: yes
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.0.1
DNS Servers: 192.168.0.1
Fallback DNS Servers: 1.1.1.1
9.9.9.10
8.8.8.8
2606:4700:4700::1111
2620:fe::10
2001:4860:4860::8888
Link 2 (enp4s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.0.1
DNS Servers: 192.168.0.1
DNS Domain: fritz.box
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d0:50:99:56:50:42 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.4/24 brd 192.168.0.255 scope global enp4s0
valid_lft forever preferred_lft forever
inet6 fe80::d250:99ff:fe56:5042/64 scope link
valid_lft forever preferred_lft forever
# drill fritz.box
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 51866
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; fritz.box. IN A
;; ANSWER SECTION:
fritz.box. 9 IN A 192.168.0.1
;; AUTHORITY SECTION:
;; ADDITIONAL SECTION:
;; Query time: 1 msec
;; SERVER: 127.0.0.53
;; WHEN: Thu Aug 20 21:40:51 2020
;; MSG SIZE rcvd: 43
# drill archlinux.de
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 24247
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; archlinux.de. IN A
;; ANSWER SECTION:
archlinux.de. 7019 IN A 176.9.50.155
;; AUTHORITY SECTION:
;; ADDITIONAL SECTION:
;; Query time: 0 msec
;; SERVER: 127.0.0.53
;; WHEN: Thu Aug 20 21:41:33 2020
;; MSG SIZE rcvd: 46
Bis hierher sieht für mich alles 100% funktionierend aus. Aber:
# ping archlinux.de
ping: connect: Das Netzwerk ist nicht erreichbar
Die Ausgaben von journalctl (gekürzt bis zum letzten Neustart des Services):
# journalctl -xeu systemd-networkd
.....
Aug 20 20:33:12 begpc systemd[1]: Starting Network Service...
░░ Subject: A start job for unit systemd-networkd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-networkd.service has begun execution.
░░
░░ The job identifier is 1561.
Aug 20 20:33:13 begpc systemd-networkd[38484]: enp4s0: Gained IPv6LL
Aug 20 20:33:13 begpc systemd-networkd[38484]: Enumeration completed
Aug 20 20:33:13 begpc systemd-networkd[38484]: enp4s0: IPv6 successfully enabled
Aug 20 20:33:13 begpc systemd[1]: Started Network Service.
░░ Subject: A start job for unit systemd-networkd.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-networkd.service has finished successfully.
░░
░░ The job identifier is 1561.
Aug 20 21:35:44 begpc systemd-networkd[38484]: lo: Reset carrier
Aug 20 21:35:44 begpc systemd-networkd[38484]: enp4s0: DHCPv6 lease lost
Aug 20 21:35:44 begpc systemd-networkd[38484]: enp4s0: Reset carrier
Aug 20 21:35:44 begpc systemd-networkd[38484]: enp4s0: No static address is stored.
Aug 20 21:35:44 begpc systemd-networkd[38484]: enp4s0: Failed
Und für resolved seit letztem Reboot:
# journalctl -xeu systemd-resolved
....
-- Reboot --
Aug 20 09:31:55 begpc systemd[1]: Starting Network Name Resolution...
░░ Subject: A start job for unit systemd-resolved.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-resolved.service has begun execution.
░░
░░ The job identifier is 91.
Aug 20 09:31:55 begpc systemd-resolved[441]: Positive Trust Anchors:
Aug 20 09:31:55 begpc systemd-resolved[441]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 20 09:31:55 begpc systemd-resolved[441]: Negative trust anchors: 10.in-addr.arpa 16.172.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 2>
Aug 20 09:31:55 begpc systemd-resolved[441]: Using system hostname 'begpc'.
Aug 20 09:31:55 begpc systemd[1]: Started Network Name Resolution.
░░ Subject: A start job for unit systemd-resolved.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-resolved.service has finished successfully.
░░
░░ The job identifier is 91.
Aug 20 13:22:56 begpc systemd-resolved[441]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.0.1.
Aug 20 13:22:56 begpc systemd-resolved[441]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.0.1.
Aug 20 14:23:38 begpc systemd-resolved[441]: Grace period over, resuming full feature set (UDP+EDNS0) for DNS server 192.168.0.1.
Aug 20 21:34:25 begpc systemd-resolved[441]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server fd00::eadf:70ff:fe44:1e1d.
Aug 20 21:37:28 begpc systemd-resolved[441]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.0.1.
Aug 20 21:46:00 begpc systemd-resolved[441]: Grace period over, resuming full feature set (UDP+EDNS0) for DNS server 192.168.0.1.