Turris not resolving its own hostname?

Software SW bugs discussion
,
1

Hey there!

I’m glad to be here, received my Turris Omnia yesterday!

I configured device using reForis with default turris hostname and this DNS configuration (DHCP server enabled):

image

So I would expect the device’s DNS to resolve turris.home to its configured IP address, so I can access the webinterface on http://turris.home/ instead of http://192.168.1.1/ - but this doesn’t work:

root@turris:~# nslookup turris
Server:         127.0.0.1
Address:        127.0.0.1#53

** server can't find turris: NXDOMAIN
** server can't find turris: NXDOMAIN
root@turris:~# nslookup turris.home
Server:         127.0.0.1
Address:        127.0.0.1#53

** server can't find turris.home: NXDOMAIN
** server can't find turris.home: NXDOMAIN

Lookup of other DHCP client hosts in the network works as expected.

Technical data:

Device             Turris Omnia Wi-Fi 6
reForis version    1.4.1
Turris OS version  6.4.4
Turris OS branch   HBS
Kernel version     5.15.135
2
3

Names should be here:

/var/hosts/dhcp.cfg01411c

It is an auto generated file.

4

Yeah, names are there, but adding this file to dnsmasq config
image
will not solve this, as Turris uses knot resolver, which isn’t configurable through GUI.

I don’t want to add a static configuration (as this might be outdated on IP address change) - and I will switch to pi-hole as DNS for the long run (which has a nice GUI for everything).

5

Similar problem was discussed here: Local DNS doesn't resolve router itself - #8 by vcunat

Myself, I managed to solve the problem on my Turris MOX just by adding router name (without .lan) and its IP into LuCI’s Network->Host names. At that moment, nslookup on the router started to resolve the router’s name. To get the same on my computer, I had to flush DNS cache. On my Ubuntu 18.04.6, it is performed by sudo systemd-resolve --flush-caches. Alternatively, you might restart the computer or wait long enough time for the cache to expire.

1 Like