fritzchentastig
Anmeldungsdatum: 15. Februar 2021
Beiträge: Zähle...
|
Ich nutze meinen Linux-Server als Nextcloud und wollte pihole als Docker installieren dies habe ich aber aufgegeben nachdem es nicht funktioniert hat.
Danach hat aber keine Domain basierte Webadresse mehr funktioniert. Ich habe das Problem versucht zu fixen und habe es auf systemd-resolved eingrenzen können. Es war deaktiviert. Aber das DNS resolving funktioniert immer noch nicht. Als ich
| systemctl status systemd-resolved
|
eingab kam follgendes zurück:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190 | ● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; ven>
Active: active (running) since Fri 2021-01-29 10:10:20 UTC; 2 weeks 2 days>
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wiki/Software/systemd/writing-network->
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver>
Main PID: 2243 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 13894)
Memory: 5.1M
CGroup: /system.slice/systemd-resolved.service
└─2243 /lib/systemd/systemd-resolved
Jan 29 10:10:20 fritzchensserver systemd[1]: Starting Network Name Resolution...
Jan 29 10:10:20 fritzchensserver systemd-resolved[2243]: Positive Trust Anchors:
Jan 29 10:10:20 fritzchensserver systemd-resolved[2243]: . IN DS 20326 8 2 e06d>
Jan 29 10:10:20 fritzchensserver systemd-resolved[2243]: Negative trust anchors>
Jan 29 10:10:20 fritzchensserver systemd-resolved[2243]: Using system hostname >
Jan 29 10:10:20 fritzchensserver systemd-resolved[2243]: DNSStubListener= is di>
Jan 29 10:10:20 fritzchensserver systemd[1]: Started Network Name Resolution.
...skipping...
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; ven>
Active: active (running) since Fri 2021-01-29 10:10:20 UTC; 2 weeks 2 days>
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wiki/Software/systemd/writing-network->
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver>
Main PID: 2243 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 13894)
Memory: 5.1M
CGroup: /system.slice/systemd-resolved.service
└─2243 /lib/systemd/systemd-resolved
Jan 29 10:10:20 fritzchensserver systemd[1]: Starting Network Name Resolution...
Jan 29 10:10:20 fritzchensserver systemd-resolved[2243]: Positive Trust Anchors:
Jan 29 10:10:20 fritzchensserver systemd-resolved[2243]: . IN DS 20326 8 2 e06d>
Jan 29 10:10:20 fritzchensserver systemd-resolved[2243]: Negative trust anchors>
Jan 29 10:10:20 fritzchensserver systemd-resolved[2243]: Using system hostname >
Jan 29 10:10:20 fritzchensserver systemd-resolved[2243]: DNSStubListener= is di>
Jan 29 10:10:20 fritzchensserver systemd[1]: Started Network Name Resolution.
~
~
ESCOC
e Resolution
/systemd-resolved.service; enabled; vendor preset: enabled)
2021-01-29 10:10:20 UTC; 2 weeks 2 days ago
e(8)
/wiki/Software/systemd/resolved
/wiki/Software/systemd/writing-network-configuration-managers
/wiki/Software/systemd/writing-resolver-clients
ved.service
-resolved
[1]: Starting Network Name Resolution...
-resolved[2243]: Positive Trust Anchors:
-resolved[2243]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc>
-resolved[2243]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17>
-resolved[2243]: Using system hostname 'fritzchensserver'.
-resolved[2243]: DNSStubListener= is disabled, but /etc/resolv.conf is a symlin>
[1]: Started Network Name Resolution.
~
~
ESCOC
or preset: enabled)
ago
onfiguration-managers
clients
4b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19>
fritzchensserver'.
abled, but /etc/resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.co>
~
~
ESCOD
e Resolution
/systemd-resolved.service; enabled; vendor preset: enabled)
2021-01-29 10:10:20 UTC; 2 weeks 2 days ago
e(8)
/wiki/Software/systemd/resolved
/wiki/Software/systemd/writing-network-configuration-managers
/wiki/Software/systemd/writing-resolver-clients
ved.service
-resolved
[1]: Starting Network Name Resolution...
-resolved[2243]: Positive Trust Anchors:
-resolved[2243]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc>
-resolved[2243]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17>
-resolved[2243]: Using system hostname 'fritzchensserver'.
-resolved[2243]: DNSStubListener= is disabled, but /etc/resolv.conf is a symlin>
[1]: Started Network Name Resolution.
~
~
lines 1-21/21 (END)
|
Ab hier komme ich nicht mehr weiter
|
lubux
Anmeldungsdatum: 21. November 2012
Beiträge: 13896
|
fritzchentastig schrieb: Aber das DNS resolving funktioniert immer noch nicht.
Wie sind die Ausgaben von:
cat /etc/systemd/resolved.conf
cat /etc/resolv.conf
ls -la /etc/resolv.conf
netstat -tulpena | grep -i 53
?
|
fritzchentastig
(Themenstarter)
Anmeldungsdatum: 15. Februar 2021
Beiträge: 27
|
Folgende
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51 | cat /etc/systemd/resolved.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details
[Resolve]
#DNS=
#FallbackDNS=
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#DNSOverTLS=no
#Cache=no-negative
DNSStubListener=no
#ReadEtcHosts=yes
carlgf@fritzchensserver:~$ cat /etc/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 "resolvectl 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
options edns0 trust-ad
search fritz.box
carlgf@fritzchensserver:~$ ls -la /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Jul 31 2020 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
carlgf@fritzchensserver:~$ netstat -tulpena | grep -i 53
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
udp 0 0 0.0.0.0:0 0.0.0.0:* 100 1379536 -
|
Im letzten habe ich die IP Gelöscht
|
lubux
Anmeldungsdatum: 21. November 2012
Beiträge: 13896
|
fritzchentastig schrieb: carlgf@fritzchensserver:~$ netstat -tulpena | grep -i 53
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
udp 0 0 0.0.0.0:0 0.0.0.0:* 100 1379536 -
Im letzten habe ich die IP Gelöscht
Warum hast Du die IP gelöscht? Was war das für eine IP? EDIT: OK, systemd-resolved sollte auf dem Port 53 (udp und tcp) lauschen, was bei dir nicht der Fall ist.
Z. B.:
:~ $ netstat -tulpena | grep -i 53
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 102 11910 -
udp 0 0 127.0.0.53:53 0.0.0.0:* 102 11909 -
|
fritzchentastig
(Themenstarter)
Anmeldungsdatum: 15. Februar 2021
Beiträge: 27
|
ich weis nicht ob das meine Heimnetz externe IP ist deswegen habe ich sie aus Sichereheitsbedenken gelöscht, da ich dachte es sei bei meiner Frage nicht wichtig
|
lubux
Anmeldungsdatum: 21. November 2012
Beiträge: 13896
|
fritzchentastig schrieb: ..., da ich dachte es sei bei meiner Frage nicht wichtig
OK, dann editiere die Datei "/etc/systemd/resolved.conf" so, dass deren Inhalt so ist:
[Resolve]
DNS=192.168.178.1 8.8.8.8 9.9.9.9
FallbackDNS=4.2.2.1 4.2.2.2
LLMNR=no
DNSStubListener=yes
Cache=yes
ReadEtcHosts=no
Domains=fritz.box
und führe danach aus:
sudo systemctl daemon-reload
sudo systemctl restart systemd-resolved
und poste danach die Ausgaben von:
systemctl status systemd-resolved
host heise.de
cat /etc/resolv.conf
sudo netstat -tulpena | grep -i 53
ls -la /etc/resolv.conf EDIT: ... und die Ausgaben von:
ls -la /run/systemd/resolve/resolv.conf
cat /run/systemd/resolve/resolv.conf
?
|
fritzchentastig
(Themenstarter)
Anmeldungsdatum: 15. Februar 2021
Beiträge: 27
|
Jetzt funktioniert apt-get update
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98 | ● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; ven>
Active: active (running) since Mon 2021-02-15 08:31:10 UTC; 47s ago
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wiki/Software/systemd/writing-network->
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver>
Main PID: 206384 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 13894)
Memory: 4.5M
CGroup: /system.slice/systemd-resolved.service
└─206384 /lib/systemd/systemd-resolved
Feb 15 08:31:10 fritzchensserver systemd[1]: Starting Network Name Resolution...
Feb 15 08:31:10 fritzchensserver systemd-resolved[206384]: Positive Trust Ancho>
Feb 15 08:31:10 fritzchensserver systemd-resolved[206384]: . IN DS 20326 8 2 e0>
Feb 15 08:31:10 fritzchensserver systemd-resolved[206384]: Negative trust ancho>
Feb 15 08:31:10 fritzchensserver systemd-resolved[206384]: Using system hostnam>
Feb 15 08:31:10 fritzchensserver systemd[1]: Started Network Name Resolution.
Feb 15 08:31:13 fritzchensserver systemd-resolved[206384]: Server returned erro>
Feb 15 08:31:13 fritzchensserver systemd-resolved[206384]: Server returned erro>
Feb 15 08:31:13 fritzchensserver systemd-resolved[206384]: Server returned erro>
...skipping...
SUMMARY OF LESS COMMANDS
Commands marked with * may be preceded by a number, N.
Notes in parentheses indicate the behavior if N is given.
A key preceded by a caret indicates the Ctrl key; thus ^K is ctrl-K.
h H Display this help.
q :q Q :Q ZZ Exit.
---------------------------------------------------------------------------
MOVING
e ^E j ^N CR * Forward one line (or N lines).
y ^Y k ^K ^P * Backward one line (or N lines).
f ^F ^V SPACE * Forward one window (or N lines).
b ^B ESC-v * Backward one window (or N lines).
z * Forward one window (and set window to N).
w * Backward one window (and set window to N).
ESC-SPACE * Forward one window, but don't stop at end-of-file.
d ^D * Forward one half-window (and set half-window to N).
u ^U * Backward one half-window (and set half-window to N).
ESC-) RightArrow * Right one half screen width (or N positions).
ESC-( LeftArrow * Left one half screen width (or N positions).
ESC-} ^RightArrow Right to last column displayed.
ESC-{ ^LeftArrow Left to first column.
F Forward forever; like "tail -f".
ESC-F Like F but stop when search pattern is found.
r ^R ^L Repaint screen.
R Repaint screen, discarding buffered input.
---------------------------------------------------
Default "window" is the screen height.
Default "half-window" is half of the screen height.
---------------------------------------------------------------------------
SEARCHING
/pattern * Search forward for (N-th) matching line.
?pattern * Search backward for (N-th) matching line.
n * Repeat previous search (for N-th occurrence).
N * Repeat previous search in reverse direction.
ESC-n * Repeat previous search, spanning files.
ESC-N * Repeat previous search, reverse dir. & spanning files.
ESC-u Undo (toggle) search highlighting.
&pattern * Display only matching lines
---------------------------------------------------
A search pattern may begin with one or more of:
^N or ! Search for NON-matching lines.
^E or * Search multiple files (pass thru END OF FILE).
^F or @ Start search at FIRST file (for /) or last file (for ?).
^K Highlight matches, but don't move (KEEP position).
^R Don't use REGULAR EXPRESSIONS.
---------------------------------------------------------------------------
JUMPING
...skipping...
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; ven>
Active: active (running) since Mon 2021-02-15 08:31:10 UTC; 47s ago
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wiki/Software/systemd/writing-network->
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver>
Main PID: 206384 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 13894)
Memory: 4.5M
CGroup: /system.slice/systemd-resolved.service
└─206384 /lib/systemd/systemd-resolved
Feb 15 08:31:13 fritzchensserver systemd-resolved[206384]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 15 08:31:13 fritzchensserver systemd-resolved[206384]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 15 08:31:13 fritzchensserver systemd-resolved[206384]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 15 08:31:13 fritzchensserver systemd-resolved[206384]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
|
|
lubux
Anmeldungsdatum: 21. November 2012
Beiträge: 13896
|
fritzchentastig schrieb: Jetzt funktioniert apt-get update
Was ist mit den anderen Ausgaben?
|
fritzchentastig
(Themenstarter)
Anmeldungsdatum: 15. Februar 2021
Beiträge: 27
|
Folgendes sind die Ausgaben
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82 | 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 Mon 2021-02-15 08:31:10 UTC; 10min 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: 206384 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 13894)
Memory: 4.5M
CGroup: /system.slice/systemd-resolved.service
└─206384 /lib/systemd/systemd-resolved
Feb 15 08:31:10 fritzchensserver systemd-resolved[206384]: Using system hostname 'fritzchensserver'.
Feb 15 08:31:10 fritzchensserver systemd[1]: Started Network Name Resolution.
Feb 15 08:31:13 fritzchensserver systemd-resolved[206384]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 15 08:31:13 fritzchensserver systemd-resolved[206384]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 15 08:31:13 fritzchensserver systemd-resolved[206384]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 15 08:31:13 fritzchensserver systemd-resolved[206384]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 15 08:41:22 fritzchensserver systemd-resolved[206384]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 15 08:41:22 fritzchensserver systemd-resolved[206384]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 15 08:41:22 fritzchensserver systemd-resolved[206384]: Using degraded feature set (UDP) for DNS server 192.168.178.1.
Feb 15 08:41:22 fritzchensserver systemd-resolved[206384]: Using degraded feature set (UDP) for DNS server 192.168.178.1.
host heise.de
heise.de has address 193.99.144.80
heise.de has IPv6 address 2a02:2e0:3fe:1001:302::
heise.de mail is handled by 10 relay.heise.de.
# 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 "resolvectl 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
options edns0 trust-ad
search fritz.box
sudo netstat -tulpena | grep -i 53
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 101 1553964 206384/systemd-reso
tcp 0 53 192.168.178.69:22 151.75.47.156:61851 FIN_WAIT1 0 0 -
tcp 0 0 127.0.0.1:36560 127.0.0.1:9982 ESTABLISHED 33 1012845 153890/Collabora_On
udp 0 0 127.0.0.53:53 0.0.0.0:* 101 1553963 206384/systemd-reso
udp 0 0 192.168.178.69:68 0.0.0.0:* 100 1379536 675/systemd-network
ls -la /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Jul 31 2020 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
ls -la /run/systemd/resolve/resolv.conf
-rw-r--r-- 1 systemd-resolve systemd-resolve 755 Feb 15 08:31 /run/systemd/resolve/resolv.conf
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.178.1
nameserver 8.8.8.8
nameserver 9.9.9.9
# Too many DNS servers configured, the following entries may be ignored.
nameserver fd00::464e:6dff:fe56:a52f
search fritz.box
|
|
lubux
Anmeldungsdatum: 21. November 2012
Beiträge: 13896
|
fritzchentastig schrieb: ls -la /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Jul 31 2020 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
ls -la /run/systemd/resolve/resolv.conf
-rw-r--r-- 1 systemd-resolve systemd-resolve 755 Feb 15 08:31 /run/systemd/resolve/resolv.conf
Lösche /etc/resolv.conf, weil es ein symlink auf "/run/systemd/resolve/stub-resolv.conf" und erstelle /etc/resolv.conf als symlink auf "/run/systemd/resolve/resolv.conf". EDIT: Siehe: https://wiki.ubuntuusers.de/ln/#Symbolische-Verknuepfungen
|
fritzchentastig
(Themenstarter)
Anmeldungsdatum: 15. Februar 2021
Beiträge: 27
|
Wie mache ich so einen Symlink?
|
fritzchentastig
(Themenstarter)
Anmeldungsdatum: 15. Februar 2021
Beiträge: 27
|
Ich bin auf diesem Link, verstehe aber Syntax nicht
|
fritzchentastig
(Themenstarter)
Anmeldungsdatum: 15. Februar 2021
Beiträge: 27
|
Habe es nun verstanden
Vielen Dank für die Hilfe
|