DNS-Resolver-BCP-TF / Resolver-Recommendations

DNS Resolver Recommendations
Creative Commons Zero v1.0 Universal
7 stars 5 forks source link

We <3 Open Source #7

Closed shane-kerr closed 1 year ago

shane-kerr commented 1 year ago

Someone needs to write some text about open source considerations

maertsen commented 1 year ago

Feel free to assign this to me. I don't have the privileges to do so myself.

Do you mean for us to write in the README.md?

shane-kerr commented 1 year ago

I'm happy either with writing in the README.md directly or with a separate file.

maertsen commented 1 year ago

some first notes

pro:

conn:

recommendation:

shane-ns1 commented 1 year ago

Recommendation: Choose any well-supported software that you are comfortable working with. Regardless of which software you choose, make sure that you have somewhere to go for support. In the case of open-source DNS software this may be financially supporting to ensure continued development. Some maintainers take donations, other offer support contracts.

There are both open source and proprietary implementations of DNS resolver software. Other modes are also possible, for example using proprietary extensions with open source software, or deploying software written in-house.

Neither open or closed licensing has any bearing on security; neither is closed less secure on principle, nor are contributions by "unknown" developers more of a risk in open source.

Benefits of open source

Drawbacks of open source

It may be worthwhile deploying software you are already running, for example a company using Microsoft systems may wish to use their resolver.

Please also consider deploying different software implementation to ensure diversity. This is discussed further in the diversity section. TODO

maertsen commented 1 year ago

PR #22 submitted; I believe we can close this issue if that work gets merged.

moonshiner commented 1 year ago

merged #22