Factory reset Turris 1.1 with OS 6.0.1, only after minimal initial configuration. If I set the local DNS suffix to ‘home.arpa’, the Knot blocks resolving local names taken from the DHCP configuration with reference to the standard Locally-Served DNS Zones. If I use, for example, the suffix ‘in.lan’, local resolving works OK. Yet, if I understand correctly, ‘home.arpa’ should be the suffix intended for local networks.
1 Like
Right. We work upstream on combining these rules better.
In the meantime, you can unblock the subtree. EDIT after months: I’m sorry, it does not work due to another issue.
- Add custom configuration file, e.g. as described on
Knot resolver (i.e. kresd) - DNS advanced settings for Omnia and MOX [Turris wiki] - Put a line into it:
policy.add(policy.suffix(policy.PASS, {todname('home.arpa.')})) - Apply, e.g. by command
/etc/init.d/resolver restart
(Queries to non-existing names may then leak to upstream resolver, contrary what the RFC requires.)
1 Like