1. 8
    1. 1

      Really great that this is possible, but these are also the sort of stories that make me appreciate the F/OSS community. I can’t imagine using an OS that requires a hack to provide private DNS. I wont judge anyone for using a closed OS, as I know I’m also a much more technical user – and I appreciate the obvious footgun that DNS changes allow for. But jeez, the amount of hacking to get this to work makes me sad.

      1. 3

        Perhaps we’ll publish a similar story for linux, but there were a bunch of dragons that needed to be slayed there too. In some ways I think it is worse since there are so many different ways to configure DNS, it can be quite complex. I wouldn’t lay all of this on a closed-source OS. :) MacOS had other challenges as did iOS and Android too.

        But - F/OSS is great, I agree! The world just wouldn’t be the same without that whole movement.

        1. 4

          You made me go ask around and dig some too, turns out systemd-resolved has a similar “routing domains” feature. Cool - decent overview here: https://systemd.io/RESOLVED-VPNS/

          1. 2

            Haha, came here to reply about systemd-resolved :D Say what you will about systemd, there are some nicely consistent things it adds to distros that use it.

            But I also agree that there are so many dragons when you start mucking about with the DNS stack. I really appreciate this work on Windows, for sure. Nice to have a clear and reproducible path to custom DNS no matter the OS!

    2. 1

      This is a hidden gem of a feature that was very timely for me. Thanks!

      1. 1

        It’s definitely not really well documented either and sadly there’s no published API for it (yet). You can use the dll in an “unpublished” way if you want, but we didn’t want to rely on that. Glad that the gem helped you out!