On Tue, 26 Sep 2023 13:35:30 +0200 Johannes Kastl <kastl@b1-systems.de> wrote:
On 26.09.23 at 13:28 Bob Williams wrote:
On Tue, 26 Sep 2023 13:09:07 +0200 Johannes Kastl <kastl@b1-systems.de> wrote:
And: Does the issue resolve after you rebooted into your Tumbleweed installation?
No the problem was still there in the Tumbleweed installation.
Check your /etc/resolv.conf. Does it contain the actual nameserver or does it use 127.0.0.1? In the latter case, dnsmasq (or similar) is involved as a plugin to NetworkManager and might be the issue.
/etc/resolv.conf lists the actual nameserver, which is pihole running on a Raspberry Pi: 192.168.178.3
Check whether you can "dig" the names directly, as soon as you notice you cannot resolve hosts.
dig @127.0.0.1 example.org (use a proper domain instead of example.org)
dig @127.0.0.1 forums.opensuse.org ... ;; no servers could be reached
dig @1.2.3.4 example.org (where 1.2.3.4 is the IP of your DNS server).
dig @192.168.178.3 forums.opensuse.org ... ;; ANSWER SECTION forums.opensuse.org. 3600 IN A 195.135.221.140
dig @5.9.164.112 example.org (or any other nameserver you trust)
dig @5.9.164.112 forums.opensuse.org ;; communications error to 5.9.164.112#53 timed out ; (1 server found) ;; no servers could be reached dig @8.8.8.8 forums.opensuse.org ... ;; ANSWER SECTION forums.opensuse.org. 1989 IN A 195.135.221.140
You can try killing the dnsmasq process (ps aux|grep dnsmasq), it should get restarted. Check if you can resolve hosts then.
I don't think it's running. That command only returns a line starting bob, not dnsmasq.
Hope this helps.
Not sure what to do with the information I have found. Kind Regards Bob -- Bob Williams No HTML please. Plain text preferred. https://useplaintext.email/ http://www.catb.org/~esr/faqs/smart-questions.html