Provide Authoritative DNS Services with NSD on Fedora 13
Updated by Linode
This guide has been deprecated and is no longer being maintained.
NSD is a lightweight yet full-featured open source name server daemon created to provide an alternative to BIND.
Before beginning, you should be familiar with basic DNS terminology and records. You will also need to ensure that your current Linode plan has enough memory to run the NSD daemon. Use the developer’s memory usage calculator to determine the memory requirement for your NSD deployment.
Install Required Software
Ensure that your package repositories are up to date and that you’ve installed all available software upgrades by issuing the following commands:
Install NSD and configure the daemon to start on boot with the following commands:
yum install nsd chkconfig nsd on
Proceed to configure the daemon.
Configure NSD Service
nsd.conf file to configure the behavior of the NSD service and the hosted DNS zones. The NSD package provides an example configuration file located at
/etc/nsd/nsd.conf that you may reference. Your file should resemble the following:
- logfile: “/var/log/nsd.log” username: nsd
Host Zones with NSD
You must specify at least one zone in the
/etc/nsd/nsd.conf file before NSD will begin serving DNS records. Refer to the following example configuration for proper syntax.
- name: example.com zonefile: /etc/nsd/example.com.zone
- name: example.org zonefile: /etc/nsd/example.org.zone
Once zones are added to the
nsd.conffile, proceed to create a zone file for each DNS zone.
Creating Zone Files
Each domain has zone file specified in the
nsd.conf file. The syntax of an NSD zone file is similar BIND zone files. Refer to the example zone files that follow for syntax, and modify domain names and IP addresses to reflect the needs of your deployment.
$ORIGIN example.com. $TTL 86400
- @ IN SOA ns1.example.com. admin.example.com. (
- 2010011801 ; serial number 28800 ; Refresh 7200 ; Retry 864000 ; Expire 86400 ; Min TTL )
- NS ns1.example.com.
- NS ns2.example.com.
MX 10 mail.example.com.
ns1 IN A 22.214.171.124 ns2 IN A 126.96.36.199 www IN A 188.8.131.52 tomato IN A 184.108.40.206 mail IN A 220.127.116.11 * IN A 18.104.22.168
$ORIGIN example.org. $TTL 86400
- @ IN SOA ns1.example.org. web-admin.example.org. (
- 2009011803 ; serial number 28800 ; Refresh 7200 ; Retry 864000 ; Expire 86400 ; Min TTL )
- NS ns1.example.org.
- NS ns2.example.org.
MX 10 mail.example.org.
- ns1 IN A 22.214.171.124
- ns2 IN A 126.96.36.199
www IN A 188.8.131.52 paisano IN A 184.108.40.206 mail IN A 220.127.116.11
pizzapie IN CNAME paisano
Rebuild the NSD database and restart the daemon with following command sequence:
nsdc rebuild /etc/init.d/nsd restart
Test the configuration and functionality of the DNS serve using
dig, which provides a command line DNS client. Issue the following command to test the DNS server:
dig @localhost www.example.org
The output should resemble the following:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
; <<>> DiG 9.6.1-P2 <<>> @localhost pizzapie.example.org ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25199 ;; flags: qr aa rd; QUERY: 1, ANSWER: 2, ORGNAMEITY: 2, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;pizzapie.example.org. IN A ;; ANSWER SECTION: pizzapie.example.org. 86400 IN CNAME paisano.example.org. paisano.example.org. 86400 IN A 18.104.22.168 ;; ORGNAMEITY SECTION: example.org. 86400 IN NS ns1.example.org. example.org. 86400 IN NS ns2.example.org. ;; Query time: 18 msec
Congratulations, you have successfully installed NSD!
Adjusting NSD for Low-Memory Situations
If you are running NSD in a low-memory environment, amending the values of the following directives in your
/etc/nsd/nsd.conf file will lower your memory and system resource usage.
ip4-only: yes tcp-count: 10 server-count: 1
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 guide is published under a CC BY-ND 4.0 license.