Use Unbound for Local DNS Resolution on Fedora 14
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
This guide has been deprecated and is no longer being maintained.
In the default configuration, Linode systems are configured to query DNS resolvers provided by Linode. If you don’t want to use a third party DNS service on your system, you may consider running an independent DNS resolving and caching service such as Unbound DNS resolver. Unbound is easy to install and configure, which makes it an ideal resolver for simple deployments.
If you are unfamiliar with DNS, you may want to consider our introduction to the DNS system. If you simply need to configure DNS services for your domain, you may want to consider using Linode’s DNS manager. If you only need to modify the behavior of DNS for a small group of systems, consider using /etc/hosts to provide this functionality.
Set the Hostname
Before you begin installing and configuring the components described in this guide, please make sure you’ve followed our instructions for setting your hostname. Issue the following commands to make sure it is set properly:
hostname hostname -f
Make sure your package repositories and installed programs are up to date by issuing the following command:
Issue the following command to install the packages for Unbound:
yum install unbound
The unbound configuration files will be located at
Following the installation, issue the following commands to start Unbound for the first time and ensure that unbound resumes following reboot:
service unbound start chkconfig unbound on
Configure Unbound Interfaces
In the default configuration, Unbound will only listen for requests on the local interface. If you want unbound to attach to additional interfaces, these interfaces must be configured manually. Possible interfaces include the public interface or the private networking interface. Specify those IP addresses after the
server: directive in the following format:
- File: /etc/unbound/unbound.conf
server: : interface: 220.127.116.11 interface: 192.168.3.105
interface: directives to reflect the actual addresses assigned to your Linode. In this example, these directives would configure Unbound to listen for requests on the publicly accessible address
18.104.22.168, and on the internal or private network address of
192.168.3.105. If you specify interfaces other than the local interface using the
interface: directive, it will disable the default local directive. If you would like to be able to perform queries on the local interface in addition to other interfaces, you will need to include an interface directive for
Control Access to your Unbound Instance
By default, Unbound will only listen for and respond to requests for DNS queries on the localhost interface (i.e. from 127.0.0.1). Unbound must be configured to listen for requests on a given interface and be configured to allow requests from a given IP address before it can successfully provide DNS services. Insert lines similar to the following example into the
unbound.conf file after the
- File: /etc/unbound/unbound.conf
server: : access-control: 127.0.0.0/8 allow access-control: 192.168.0.0/16 allow\_snoop access-control: 22.214.171.124/32 allow access-control: 126.96.36.199/24 deny access-control: 188.8.131.52/8 refuse
Unbound uses CIDR notation to control access to the DNS resolver. This allows you permit or refuse DNS traffic to large or small groups of IP addresses in a simple and clear syntax. In the example above, you can see a number of different access control approaches.
The first example will allow all requests from the
127.0.0.0/8 range, which covers all requests from localhost. This behavior mimics the default behavior of Unbound. The next example includes the
192.168.0.0/16 net block, or all IP addresses beginning with
192.168., which corresponds to the local “private” network. Specify this if you have private networking configured on your Linode and would like to allow multiple Linodes in the same data center to resolve domain addresses using your server.
The next example will allow all requests from the IP address
184.108.40.206. To specify IP addresses in CIDR notation, simply append
/32 to the desired IP address. The remaining examples force Unbound to block access from two netblocks, or all IP addresses that begin with
12.34.56. and the entire
34. block. Specifying
deny causes Unbound to drop all traffic from this address or addresses. By contrast, the
refuse option returns an error message in response to requests from blocked sources.
To summarize, there are four possible access control behaviors:
- Unbound can
allow_snooptraffic. This means that both recursive and nonrecursive requests will be filled when they originate from IP addresses belonging to specified netblocks. Nonrecursive request are needed to provide additional information for some tools, such as the
+traceoption of the
- Unbound can
allowtraffic. This means that recursive requests will be filled when they originate from IP addresses belonging to specified netblocks.
- Unbound can
denytraffic. In this case, unbound will simply drop traffic and offer no error message.
- Unbound can
refusetraffic. This causes Unbound to send an error message in response to requests from disallowed sources.
When you have configured your Unbound server to acceptable parameters, issue the following command to restart Unbound:
service unbound restart
Unbound is now active and functional.
Configure your System to Resolve DNS Using Unbound
Before you can begin using your Unbound instance to resolve DNS queries, you need to configure your
/etc/resolv.conf file to point to the new resolver. You can remove all existing lines from this file or comment them by prepending hash marks (
#) to every line.
If you’re accessing your Unbound instance over the local interface, make sure your
/etc/resolv.conf resembles the following:
Important: By default, Linodes use DHCP to assign networking settings, including the public IP address and DNS resolvers. For any systems that you intend to use a custom resolver with, you must follow our instructions for
static networking. This will prevent your
/etc/resolv.conf file getting overwritten with the default resolvers after a system reboot.
- File: /etc/resolve.conf
If you access Unbound from another machine, modify the address to reflect the address that Unbound is configured to receive requests. Ensure that Unbound’s access control rules permit access from all clients that will be making requests from the server. If your Unbound instance is accessible on the public network, you can configure any machine on the Internet to resolve DNS using your Linode. While most Linux-based systems use the
/etc/resolve.conf method for configuring DNS resolution, consult your operating system’s networking configuration interface to reconfigure your DNS settings.
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on