On Wed, Mar 31, 2021 at 01:42:36PM +0200, Moritz Kempe wrote: > > grep ^hosts: /etc/nsswitch.conf > -- > hosts: files mdns4_minimal [NOTFOUND=return] dns mymachines
I don't know what "mymachines" is. I don't see it in the man page. What happens if you get rid of the "mymachines" field? > -rw-r--r-- 1 root root 54 Mar 31 13:28 /etc/resolv.conf > domain fritz.box > search fritz.box > nameserver 10.0.0.1 You're using a local caching resolver, or at least something that forwards requests. That's fine, if it works. You might try probing the DNS resolver at 10.0.0.1 to see whether it actually does work. (There's a really good chance that 10.0.0.1 is your router, and that your router implements a forwarding nameserver, which just passes your requests to your ISP. These router-based forwarding resolvers can be a bit flaky sometimes.) > ; <<>> DiG 9.16.13-Debian <<>> @8.8.8.8 www.debian.org > ; (1 server found) > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20269 > ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 512 > ;; QUESTION SECTION: > ;www.debian.org. IN A > > ;; ANSWER SECTION: > www.debian.org. 229 IN A 130.89.148.77 > www.debian.org. 229 IN A 149.20.4.15 > www.debian.org. 229 IN A 128.31.0.62 > > ;; Query time: 35 msec > ;; SERVER: 8.8.8.8#53(8.8.8.8) > ;; WHEN: Wed Mar 31 13:38:10 CEST 2021 > ;; MSG SIZE rcvd: 91 That's good. At least you're not blocking UDP packets or something like that. If the weird entry in nsswitch.conf doesn't turn out to be the problem, and 10.0.0.1 turns out to be non-functional in some way, you could use Google's resolvers as a fallback.
