Ich habe wahrscheinlich ein Problem mit dem systemd-resolved : er fällt auf die degraded dns resolution zurück.
Die Suche im Internet hat mir leider nicht weitergeholfen. Kann mir jemand bitte sagen, wie ich das "Using degraded feature set (UDP) for DNS server 192.168.1.1.", das im ersten Quote zu sehen ist fixen kann? Die anderen Quotes sollen dazu dienen, die aktuelle Konfiguration darzulegen.
Code
$ sudo systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2019-01-23 16:21:55 CET; 28min ago
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 905 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 2305)
CGroup: /system.slice/systemd-resolved.service
└─905 /lib/systemd/systemd-resolved
jan 23 16:21:55 silver systemd[1]: Starting Network Name Resolution...
jan 23 16:21:55 silver systemd-resolved[905]: Positive Trust Anchors:
jan 23 16:21:55 silver systemd-resolved[905]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200
jan 23 16:21:55 silver systemd-resolved[905]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc
jan 23 16:21:55 silver systemd-resolved[905]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17
jan 23 16:21:55 silver systemd-resolved[905]: Using system hostname 'silver'.
jan 23 16:21:55 silver systemd[1]: Started Network Name Resolution.
jan 23 16:21:55 silver systemd-resolved[905]: Using degraded feature set (UDP) for DNS server 192.168.1.1.
jan 23 16:42:09 silver systemd-resolved[905]: Grace period over, resuming full feature set (UDP+EDNS0) for D
jan 23 16:49:39 silver systemd-resolved[905]: Using degraded feature set (UDP) for DNS server 192.168.1.1.sudo systemctl status systemd-networkd
Code
$ sudo systemctl status systemd-networkd
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2019-01-23 16:21:55 CET; 31min ago
Docs: man:systemd-networkd.service(8)
Main PID: 873 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 2305)
CGroup: /system.slice/systemd-networkd.service
└─873 /lib/systemd/systemd-networkd
jan 23 16:21:55 silver systemd[1]: Starting Network Service...
jan 23 16:21:55 silver systemd-networkd[873]: Enumeration completed
jan 23 16:21:55 silver systemd[1]: Started Network Service.
jan 23 16:21:55 silver systemd-networkd[873]: lo: Link is not managed by us
jan 23 16:21:55 silver systemd-networkd[873]: enp0s10: IPv6 successfully enabled
jan 23 16:21:55 silver systemd-networkd[873]: enp0s10: Gained carrier
jan 23 16:21:55 silver systemd-networkd[873]: enp0s10: DHCPv4 address 192.168.1.45/24 via 192.168.1.1
jan 23 16:21:56 silver systemd-networkd[873]: enp0s10: Gained IPv6LL
jan 23 16:21:56 silver systemd-networkd[873]: enp0s10: ConfiguredCode
$ ll /etc/resolv*
lrwxrwxrwx 1 root root 39 oct 6 14:33 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.confCode
$ ll /run/systemd/resolve/*
-rw-r--r-- 1 systemd-resolve systemd-resolve 605 jan 23 16:21 /run/systemd/resolve/resolv.conf
-rw-r--r-- 1 systemd-resolve systemd-resolve 718 jan 23 16:21 /run/systemd/resolve/stub-resolv.confCode
$ cat /run/systemd/resolve/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# 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 192.168.1.1
search fritz.boxCode
$ cat /run/systemd/resolve/stub-resolv.conf
# 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 fritz.boxCode
$ sudo systemd-resolve --status
Global
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 2 (enp0s10)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.1.1
DNS Domain: fritz.boxCode
$ ll /etc/netplan/*
-rw-r--r-- 1 root root 161 jan 18 15:10 /etc/netplan/01-netcfg.yamlCode
$ cat /etc/netplan/01-netcfg.yaml
network:
version: 2
renderer: networkd
ethernets:
enp0s10:
match:
macaddress: 00:25:22:88:f2:bf
dhcp4: true
wakeonlan: true
Vielen Dank im Voraus.
