Code: Select all
Host or domain name not found. Name service error for name=freenet.de type=MX: Host not found, try again
Code: Select all
Host or domain name not found. Name service error for name=freenet.de type=MX: Host not found, try again
Code: Select all
host freenet.de
freenet.de has address 62.104.23.16
freenet.de mail is handled by 1 emig.freenet.de.
host emig.freenet.de
emig.freenet.de has address 195.4.92.215
emig.freenet.de has address 195.4.92.216
emig.freenet.de has address 195.4.92.217
emig.freenet.de has IPv6 address 2001:748:100:40::8:116
emig.freenet.de has IPv6 address 2001:748:100:40::8:117
emig.freenet.de has IPv6 address 2001:748:100:40::8:115
Code: Select all
host freenet.de
;; communications error to 2001:41d0:3:163::1#53: timed out
;; communications error to 213.186.33.99#53: timed out
;; no servers could be reached
Code: Select all
host emig.freenet.de
;; communications error to 2001:41d0:3:163::1#53: timed out
;; communications error to 2001:41d0:3:163::1#53: timed out
;; communications error to 213.186.33.99#53: timed out
;; no servers could be reached
Code: Select all
nameserver 2001:41d0:3:163::1
nameserver 213.186.33.99
Code: Select all
Current DNS Server: 213.186.33.99
DNS Servers: 2001:41d0:3:163::1 213.186.33.99
Code: Select all
file /etc/resolv.conf
Code: Select all
/etc/resolv.conf: symbolic link to /run/systemd/resolve/stub-resolv.conf
Code: Select all
file /etc/resolv.conf
Code: Select all
/etc/resolv.conf: symbolic link to /run/systemd/resolve/resolv.conf
Code: Select all
systemctl status systemd-resolved.service
Code: Select all
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
Active: active (running) since Thu 2024-02-15 13:06:51 UTC; 2 weeks 6 days ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 559 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 38030)
Memory: 5.0M
CPU: 56.144s
CGroup: /system.slice/systemd-resolved.service
└─559 /lib/systemd/systemd-resolved
Feb 15 13:06:51 n7.ip-144-217-75.net systemd[1]: Starting systemd-resolved.service - Network Name Res>
Feb 15 13:06:51 n7.ip-144-217-75.net systemd-resolved[559]: Positive Trust Anchors:
Feb 15 13:06:51 n7.ip-144-217-75.net systemd-resolved[559]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0>
Feb 15 13:06:51 n7.ip-144-217-75.net systemd-resolved[559]: Negative trust anchors: home.arpa 10.in-a>
Feb 15 13:06:51 n7.ip-144-217-75.net systemd-resolved[559]: Using system hostname 'ns7.ip-144-21>
Feb 15 13:06:51 n7.ip-144-217-75.net systemd[1]: Started systemd-resolved.service - Network Name Reso>
Feb 15 13:07:27 n7.ip-144-217-75.net systemd-resolved[559]: Clock change detected. Flushing caches.
lines 1-22/22 (END)
Ja, wäre es. Aber nicht weise.
Code: Select all
systemctl restart systemd-resolved.service
systemctl status systemd-resolved.service