Next edit the default config for unbound vi /etc/default/unbound Notice we turned on the chroot option, and few other hardening options for security. It’s a long, well commented config file, but all you need to get started is: interface: 0.0.0.0 Thrilling, I know! Next up lets modify unbound’s config. So first we’ll install Unbound, it’s as easy as… apt-get install unbound My install is going to be in Debian 6.0 (Squeeze), but it should be identical for Ubuntu Linux users, and for any other Linux users, after the Unbound is installed.
The next article in this series will deal with implementing DNSCrypt, and later DNSSEC. In this article I'll share how I've setup Unbound running as a local, caching, recurisve DNS server in chroot. The source code is under a BSD License._" Besides that the project has ties to some OpenBSD people, which bodes well for its security focus, and even has an option to chroot the install in the configuration file. Unbound is designed as a set of modular components, so that also DNSSEC (secure DNS) validation and stub-resolvers (that do not run as a server, but are linked into an application) are easily possible. Unbound () as "_.a validating, recursive, and caching DNS resolver. So, first up, before getting DNSCrypt (and later ()) I need to have a good install of a local DNS server to handle things, and I've setted on using ().
So I knew it was time to take things more seriously so I could properly run DNSCrypt as part of my DNS stack. When I tried out () from the () folks, I emailed them and asked if it was available to run on a server, and sure enough, they have it in their (), ready to compile in Linux. I want to run my own DNS server, while I've done this before it was always a one off that I never spent much time researching or implementing it as well, and securely, as I wanted.
0 kommentar(er)
