This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
en:howto:dns [2018/01/15 15:30] nkoranova [DNS and forwarding] |
en:howto:dns [2019/03/23 22:10] jschlehofer |
||
---|---|---|---|
Line 7: | Line 7: | ||
The operating system [[https://openwrt.org/|OpenWRT]], which Turris OS is based on, has in it‘s default configuration dnsmasq in the role of DNS and DHCP server. Dnsmasq stays on Turris, but only in the role of the DHCP server. Turris and Omnia substitute the DNS resolver with a different implementation: | The operating system [[https://openwrt.org/|OpenWRT]], which Turris OS is based on, has in it‘s default configuration dnsmasq in the role of DNS and DHCP server. Dnsmasq stays on Turris, but only in the role of the DHCP server. Turris and Omnia substitute the DNS resolver with a different implementation: | ||
- | - Turris uses the DNS resolver [[https://unbound.nlnetlabs.nl/|Unbound]] | + | - Turris 1.0, 1.1 uses the DNS resolver [[https://unbound.nlnetlabs.nl/|Unbound]] |
- | - Omnia uses the DNS resolver [[https://www.knot-resolver.cz/|Knot resolver]] (also known under the abbreviation ''kresd''). | + | - Turris Omnia, Turris MOX uses the DNS resolver [[https://www.knot-resolver.cz/|Knot Resolver]] (also known under the abbreviation ''kresd''). |
That is the reason why changes made in the DNS settings in [[en:howto:ssh#pristup_k_rozhrani_luci|LuCI]] won‘t manifest. | That is the reason why changes made in the DNS settings in [[en:howto:ssh#pristup_k_rozhrani_luci|LuCI]] won‘t manifest. | ||