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?
Trying "sshgw.tier1.internal" ;; connection timed out; no servers could be reached
Ia am confused also by the dot after "internal".
To my knowledge a trailing . should tell the local resolver that this is the fqdn, do not try to add search domain specified /etc/resolv.conf - but in this case I get the same result anyway.
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 Trying "isengard.valinor" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53476 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;isengard.valinor. IN A ;; ANSWER SECTION: isengard.valinor. 63816 IN A 192.168.1.16 Received 50 bytes from 127.0.0.1#53 in 0 ms Trying "isengard.valinor" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30448 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;isengard.valinor. IN AAAA Received 34 bytes from 127.0.0.1#53 in 0 ms Trying "isengard.valinor" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35860 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;isengard.valinor. IN MX ;; AUTHORITY SECTION: valinor. 86400 IN SOA telcontar.valinor. root.Telcontar.valinor. 2023050314 28800 7200 604800 86400 Received 102 bytes from 127.0.0.1#53 in 4 ms cer@Telcontar:~> Ok, the second time it is trying AAAA and then MX. I'm a bit confused myself.
In contrast, if I try to resolve a external domain, it works perfectly well:
localadm@sshgw:~> time host software.opensuse.org software.opensuse.org is an alias for obs-login.opensuse.org. obs-login.opensuse.org has address 195.135.223.221 obs-login.opensuse.org has IPv6 address 2a07:de40:b250:131:10:151:131:20
real 0m0,110s user 0m0,015s sys 0m0,018s localadm@sshgw:~>
-- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)