Control over client DNS servers

**Maintainer note:** If you are interested in this feature, please give it a thumbs up. It's also helpful if you state your requirements in the comments (e.g. Windows, macOS, or Linux - and which distro or DNS config you're using today; whether you care about catch-all or split-DNS, etc.) --- It's be great if, on connection to a nebula mesh, the DNS servers of the client could be modified. Specifically, _not_ to the DNS server served by Nebula, as this just serves the hostnames of the other nodes from the lighthouse. I'm imagining this working much like the `DNS` key in a wireguard config ([man page for reference](https://git.zx2c4.com/wireguard-tools/about/src/man/wg-quick.8)). On connection, the DNS servers the client uses are modified based on those specified in the client config. These settings would not be pushed down by the lighthouse (although perhaps they could / should be?). On disconnect, these settings would be restored to the system default. For versatility, I don't think these DNS servers should be constrained to nodes. It's possible to achieve this currently by wrapping the nebula command and using `resolvconf` on Linux, but this is far from being both universal, and cross-platform. Doing a custom solution on mobile is especially difficult!

Posted by RealOrangeOne on Oct 20, 2020, 2:21 PM

Tags

• reliability (Network)

Related issues

• I can't recall who said it, but "The biggest problem with golden ages is that you never realize you're in one until it's over".
• [BUG] No response from API error when Advisor is triggered
• I thought the general premise is that humans can't form social groups bigger than around ~200.
• great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things.
• > It's only with the emergence of whiny, persnickety Unix devs who refused to leave the comforting embrace of their editor of choice that...
• Contrary to some other comments: no, IPV6 hasn't taken over the world at all.