Troubleshooting • DNS don't work

Code:

pi@raspberrypi:~ $ ping -c2 google.frping: google.fr: Échec temporaire dans la résolution du nompi@raspberrypi:~ $ ping -c2 google.comping: google.com: Échec temporaire dans la résolution du nompi@raspberrypi:~ $ ping -c2 8.8.8.8PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.64 bytes from 8.8.8.8: icmp_seq=2 ttl=115 time=11.3 msFrom 192.168.3.132 icmp_seq=1 Destination Host Unreachable--- 8.8.8.8 ping statistics ---2 packets transmitted, 1 received, +1 errors, 50% packet loss, time 1021msrtt min/avg/max/mdev = 11.340/11.340/11.340/0.000 ms, pipe 2pi@raspberrypi:~ $ dig google.com; <<>> DiG 9.16.48-Raspbian <<>> google.com;; global options: +cmd;; connection timed out; no servers could be reachedpi@raspberrypi:~ $ 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]# Some examples of DNS servers which may be used for DNS= and FallbackDNS=:# Cloudflare: 1.1.1.1 1.0.0.1 2606:4700:4700::1111 2606:4700:4700::1001# Google:     8.8.8.8 8.8.4.4 2001:4860:4860::8888 2001:4860:4860::8844# Quad9:      9.9.9.9 2620:fe::fe#DNS=#FallbackDNS=#Domains=#DNSSEC=no#DNSOverTLS=no#MulticastDNS=yes#LLMNR=yes#Cache=yes#DNSStubListener=yes#DNSStubListenerExtra=#ReadEtcHosts=yes#ResolveUnicastSingleLabel=noDNS=1.1.1.1 192.168.1.1pi@raspberrypi:~ $ 

Code:

pi@raspberrypi:~ $ sudo systemctl restart systemd-resolved.servicepi@raspberrypi:~ $ dig google.fr; <<>> DiG 9.16.48-Raspbian <<>> google.fr;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40064;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1;; OPT PSEUDOSECTION:; EDNS: version: 0, flags:; udp: 65494;; QUESTION SECTION:;google.fr.INA;; ANSWER SECTION:google.fr.79INA172.217.18.227;; Query time: 20 msec;; SERVER: 127.0.0.53#53(127.0.0.53);; WHEN: Thu Apr 18 08:56:58 CEST 2024;; MSG SIZE  rcvd: 54pi@raspberrypi:~ $ 

Code:

pi@raspberrypi:~ $ journalctl -xe░░ L'unité (unit) resolvconf-pull-resolved.path a terminé son démarrage, avec le résultat done.avril 18 08:56:52 raspberrypi systemd[1]: Starting Network Name Resolution...░░ Subject: L'unité (unit) systemd-resolved.service a commencé à démarrer░░ Defined-By: systemd░░ Support: https://www.debian.org/support░░ ░░ L'unité (unit) systemd-resolved.service a commencé à démarrer.avril 18 08:56:52 raspberrypi systemd-resolved[1122]: Positive Trust Anchors:avril 18 08:56:52 raspberrypi systemd-resolved[1122]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8davril 18 08:56:52 raspberrypi systemd-resolved[1122]: 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.arp>avril 18 08:56:53 raspberrypi systemd-resolved[1122]: Using system hostname 'raspberrypi'.avril 18 08:56:53 raspberrypi systemd[1]: Started Network Name Resolution.░░ Subject: L'unité (unit) systemd-resolved.service a terminé son démarrage░░ Defined-By: systemd░░ Support: https://www.debian.org/support░░ ░░ L'unité (unit) systemd-resolved.service a terminé son démarrage, avec le résultat done.avril 18 08:56:53 raspberrypi systemd[1]: Reached target Host and Network Name Lookups.░░ Subject: L'unité (unit) nss-lookup.target a terminé son démarrage░░ Defined-By: systemd░░ Support: https://www.debian.org/support░░ ░░ L'unité (unit) nss-lookup.target a terminé son démarrage, avec le résultat done.avril 18 08:56:53 raspberrypi systemd[1]: Starting resolvconf-pull-resolved.service...░░ Subject: L'unité (unit) resolvconf-pull-resolved.service a commencé à démarrer░░ Defined-By: systemd░░ Support: https://www.debian.org/support░░ ░░ L'unité (unit) resolvconf-pull-resolved.service a commencé à démarrer.avril 18 08:56:53 raspberrypi systemd[1]: resolvconf-pull-resolved.service: Succeeded.░░ Subject: Unit succeeded░░ Defined-By: systemd░░ Support: https://www.debian.org/support░░ ░░ The unit resolvconf-pull-resolved.service has successfully entered the 'dead' state.avril 18 08:56:53 raspberrypi systemd[1]: Finished resolvconf-pull-resolved.service.░░ Subject: L'unité (unit) resolvconf-pull-resolved.service a terminé son démarrage░░ Defined-By: systemd░░ Support: https://www.debian.org/support░░ ░░ L'unité (unit) resolvconf-pull-resolved.service a terminé son démarrage, avec le résultat done.avril 18 08:57:15 raspberrypi systemd-timesyncd[444]: Timed out waiting for reply from 194.57.169.1:123 (2.debian.pool.ntp.org).avril 18 08:57:38 raspberrypi systemd-timesyncd[444]: Initial synchronization to time server 162.19.224.29:123 (2.debian.pool.ntp.org).pi@raspberrypi:~ $