Hi I have now run into at situation with some OpenSUSE machines on a friends network. They are on a separate LAN and a pfSense manages firewalling, dhcp and dns. Except that we have had one problem after another with the build in resolver. So I thought 🤔 how hard can it be to run your own resolver? I spun up another OpenSUSE with dnsmasq. I am new to dnsmasq but I don't think that's the problem. Now I can perform a dig command from another machine to my new resolver and get a answer immediately: localadm@sshgw:~> time dig @192.168.80.4 -x 192.168.80.8 +short sshgw.tier1.internal. real 0m0,033s .. localadm@sshgw:~> time dig @192.168.80.4 sshgw.tier1.internal. +short 192.168.80.8 real 0m0,033s No problem here, and I then went on to configure the networking on the other machines using yast and wicked in control. localadm@sshgw:~> cat /etc/resolv.conf # blabla search tier1.internal nameserver 192.168.80.4 localadm@sshgw:~> grep host /etc/nsswitch.conf hosts: files mdns_minimal [NOTFOUND=return] dns But when I test using using the host command: localadm@sshgw:~> host sshgw.tier1.internal. sshgw.tier1.internal has address 192.168.80.8 ;; connection timed out; no servers could be reached ;; connection timed out; no servers could be reached It responds immediately with the correct answer, but then hangs a while before the timeout lines... I must have overlooked something basic, but what? -- Klaus