lubux schrieb:
thom_raindog schrieb:
Nein. 99 ist mein PiHole, die PCs liegen alle über 100.
D. h. die Ausgabe von tcpdump war von deinem PI und nicht von deinem PC.
Korrekt. So hattest du es ja auch geschrieben ☺
Wie sind auf deinem PI (mit PiHole), jetzt die Ausgaben von:
host -t a heise.de 80.241.218.68
host -t a heise.de 1.1.1.1
?
host -t a heise.de 80.241.218.68
;; connection timed out; no servers could be reached
host -t a heise.de 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
heise.de has address 193.99.144.80
Heißt, der DNS-Server von DisMail mag mich nicht? Ich stelle PiHole gleich mal auf nen anderen Anbieter um, mal sehen.
@ChickenLipsRfun2eat
systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-05-26 11:24:08 CEST; 12min 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: 586 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 4588)
Memory: 8.4M
CGroup: /system.slice/systemd-resolved.service
└─586 /lib/systemd/systemd-resolved
Mai 26 11:24:07 Laptop systemd[1]: Starting Network Name Resolution...
Mai 26 11:24:08 Laptop systemd-resolved[586]: Positive Trust Anchors:
Mai 26 11:24:08 Laptop systemd-resolved[586]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Mai 26 11:24:08 Laptop systemd-resolved[586]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.>
Mai 26 11:24:08 Laptop systemd-resolved[586]: Using system hostname 'Laptop'.
Mai 26 11:24:08 Laptop systemd[1]: Started Network Name Resolution.
Mai 26 11:24:12 Laptop systemd-resolved[586]: Using degraded feature set (UDP) for DNS server 192.168.0.1.
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
grep hosts /etc/nsswitch.conf
hosts: files mdns4_minimal [NOTFOUND=return] dns
ip r
default via 192.168.0.1 dev wlp2s0 proto static metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.240 metric 600
Das ist jetzt alles vom Laptop, der ist aber identisch betroffen, wie der PC - Namensauflösung geht nur über die FritzBox.