Turris can't nslookup unamglobal.unam.mx, other things work (?)

Software SW help
1

My turris router can’t look up unamglobal.unam.mx. Forwarding is off.
Upstream modem IP addresses are detailed below from /tmp/resolv.conf.d/resolv.conf.auto

Forus has:

image
image721×224 12.3 KB

See below which seems consistent and repeatable:

root@turris:~# nslookup unamglobal.unam.mx
;; connection timed out; no servers could be reached

And then:

root@turris:~# nslookup www.anz.com
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: www.anz.com
www.anz.com canonical name = ksjnk4a.x.incapdns.net
Name: ksjnk4a.x.incapdns.net
Address 1: 45.60.126.46
www.anz.com canonical name = ksjnk4a.x.incapdns.net

root@turris:~# nslookup ipv6.google.com
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: ipv6.google.com
ipv6.google.com canonical name = ipv6.l.google.com
Name: ipv6.google.com
ipv6.google.com canonical name = ipv6.l.google.com
Name: ipv6.l.google.com
Address 1: 2404:6800:4006:814::200e

root@turris:~# cat /tmp/resolv.conf.d/resolv.conf.auto

Interface wan

nameserver 192.168.0.1
search gateway

Interface wan6

nameserver 2001:8004:1b30:c8e::1

root@turris:~# nslookup www.google.com 192.168.0.1
Server: 192.168.0.1
Address: 192.168.0.1#53

Name: www.google.com
Address 1: 142.250.76.100
Address 2: 2404:6800:4006:80f::2004

root@turris:~# nslookup unamglobal.unam.mx 192.168.0.1
Server: 192.168.0.1
Address: 192.168.0.1#53

Name: unamglobal.unam.mx
Address 1: 132.248.10.233
Address 2: 2001:8004:11d0:4e2a::84f8:ae9

root@turris:~# ping -c 1 2001:8004:1b30:c8e::1
PING 2001:8004:1b30:c8e::1(2001:8004:1b30:c8e::1) 56 data bytes

— 2001:8004:1b30:c8e::1 ping statistics —
1 packets transmitted, 0 received, 100% packet loss, time 0ms
,

2

I don’t know. The name resolves on my Omnias without issues. (same reForis setting)

3

Could this be something to do with the fact that for some reason, the IPV6 address (2001:8004:1b30:c8e::1) of the upstream modem’s DNS server is not accessible or pingable as above?

4

No, it’s unused as you turned forwarding off.

5

Theoretically some bug in nslookup. I wouldn’t recommend it, especially the one by default on Turris (coming from busybox).