Den 05.08.2024 kl. 03.22 skrev Carlos E. R.:
On 2024-08-05 00:28, Klaus Vink Slott via openSUSE Users wrote:
On 04.08.2024 kl. 21.24 Carlos E. R. wrote:
On 2024-08-04 20:31, Klaus Vink Slott via openSUSE Users wrote:
...
But when I test using using the host command: localadm@sshgw:~> host sshgw.tier1.internal.
you could try adding "-v". Maybe that gives information about where it gets stuck: Did not know about that, thanks. With verbose added I get:
localadm@sshgw:~> host -v sshgw.tier1.internal. Trying "sshgw.tier1.internal" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43751 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION: ;sshgw.tier1.internal. IN A
;; ANSWER SECTION: sshgw.tier1.internal. 0 IN A 192.168.80.8
Received 54 bytes from 192.168.80.4#53 in 0 ms Trying "sshgw.tier1.internal" ;; connection timed out; no servers could be reached
Huh? ...
The question is, why is the local resolver not satisfied with the first result?
I don't know. Let me try with one of mine and compare.
cer@Telcontar:~> host -v isengard.valinor ...
Ok, the second time it is trying AAAA and then MX.
Bingo! It is searching for a IPv6 address, and I have totally ignored all IPv6 related configuration, when configuring the resolver. Also confirmed by the test suggested by erwinl@dds.nl in another answer. Thanks for your input. This behavior really confused me. -- Klaus