Setting up nsd DNS server - Revision history

Sertonix: replace /etc/init.d with rc-service

2023-11-17T10:32:02Z

replace /etc/init.d with rc-service

← Older revision		Revision as of 10:32, 17 November 2023
Line 99:		Line 99:
	{{Cmd\|nsdc rebuild}}		{{Cmd\|nsdc rebuild}}
	Finally, start the server and set it to auto-start:		Finally, start the server and set it to auto-start:
	{{Cmd\|~~/etc/init.d/~~nsd start		{{Cmd\|rc-service nsd start
	rc-update add nsd}}		rc-update add nsd}}

Sertonix: update link

2023-08-25T21:44:19Z

update link

← Older revision		Revision as of 21:44, 25 August 2023
Line 1:		Line 1:
	[~~http~~://www.nlnetlabs.nl/projects/nsd/ NSD] is an authoritative-only DNS server. The following page shows how to setup a single-zone configuration, with one server being a master where updates are made, and a slave which will have changes replicated to it automatically. In the examples 10.1.0.1 is used as the master server's IP address, 10.2.0.1 is the slave address. The IP addresses used here (along with the domain) should be replaced with the IP addresses of your servers.		[https://www.nlnetlabs.nl/projects/nsd/about/ NSD] is an authoritative-only DNS server. The following page shows how to setup a single-zone configuration, with one server being a master where updates are made, and a slave which will have changes replicated to it automatically. In the examples 10.1.0.1 is used as the master server's IP address, 10.2.0.1 is the slave address. The IP addresses used here (along with the domain) should be replaced with the IP addresses of your servers.

	= Install =		= Install =

Bt129 at 09:47, 26 July 2021

2021-07-26T09:47:47Z

← Older revision		Revision as of 09:47, 26 July 2021
Line 1:		Line 1:
	[http://www.nlnetlabs.nl/projects/nsd/ NSD] is an authoritative-only DNS server. The following page shows how to setup a single-zone configuration, with one server being a master where updates are made, and a slave which will have changes replicated to it automatically. In the examples 10.1.0.1 is used as the master server's IP, ~~while~~ 10.2.0.1 is the slave. The IP addresses used here (along with the domain) should be replaced with the ~~proper~~ IP addresses of your servers.		[http://www.nlnetlabs.nl/projects/nsd/ NSD] is an authoritative-only DNS server. The following page shows how to setup a single-zone configuration, with one server being a master where updates are made, and a slave which will have changes replicated to it automatically. In the examples 10.1.0.1 is used as the master server's IP address, 10.2.0.1 is the slave address. The IP addresses used here (along with the domain) should be replaced with the IP addresses of your servers.

	= Install =		= Install =
Line 28:		Line 28:
	provide-xfr: 10.2.0.1 sec_key		provide-xfr: 10.2.0.1 sec_key
	</pre>		</pre>
	~~Then,~~ create the zone file for the zone in question (/etc/nsd/alpinelinux.org.zone in this case):		Next create the zone file for the zone in question (/etc/nsd/alpinelinux.org.zone in this case):
	<pre>		<pre>

Line 71:		Line 71:
	</pre>		</pre>

	~~Next, on~~ the slave server, ~~setup~~ /etc/nsd/nsd.conf:		On the slave server, set up /etc/nsd/nsd.conf:
	<pre>		<pre>
	server:		server:
Line 91:		Line 91:
	request-xfr: AXFR 10.1.0.1 sec_key		request-xfr: AXFR 10.1.0.1 sec_key
	</pre>		</pre>
	Create the zone file /etc/nsd/alpinelinux.org.zone as well on the slave.		Create the zone file /etc/nsd/alpinelinux.org.zone as well, on the slave.

	= Start Server =		= Start Server =
	First step, make sure you ~~didn~~'t have any typos in your ~~configuration~~ (on both boxes):		First step, make sure you don't have any typos in your configurations (on both boxes):
	{{Cmd\|nsd-checkconf /etc/nsd/nsd.conf}}		{{Cmd\|nsd-checkconf /etc/nsd/nsd.conf}}
	Then each time a change is made to the zone (including when you first start the server), you need to rebuild the NSD zone databases:		Then each time a change is made to the zone (including when you first start the server), you need to rebuild the NSD zone databases:

Fab at 05:09, 26 March 2012

2012-03-26T05:09:26Z

← Older revision		Revision as of 05:09, 26 March 2012
Line 1:		Line 1:
	NSD is an authoritative-only DNS server. The following page shows how to setup a single-zone configuration, with one server being a master where updates are made, and a slave which will have changes replicated to it automatically. In the examples 10.1.0.1 is used as the master server's IP, while 10.2.0.1 is the slave. The IP addresses used here (along with the domain) should be replaced with the proper IP addresses of your servers.		[http://www.nlnetlabs.nl/projects/nsd/ NSD] is an authoritative-only DNS server. The following page shows how to setup a single-zone configuration, with one server being a master where updates are made, and a slave which will have changes replicated to it automatically. In the examples 10.1.0.1 is used as the master server's IP, while 10.2.0.1 is the slave. The IP addresses used here (along with the domain) should be replaced with the proper IP addresses of your servers.

	= Install =		= Install =

Dubiousjim: Category:Networking

2012-03-12T07:13:13Z

Category:Networking

← Older revision		Revision as of 07:13, 12 March 2012
Line 103:		Line 103:

	{{Tip\|You've now got a set of DNS servers that will each answer with authoritative data for the given zone, and whenever updates are made to the master server, they are replicated using a zone transfer to the slave box.}}		{{Tip\|You've now got a set of DNS servers that will each answer with authoritative data for the given zone, and whenever updates are made to the master server, they are replicated using a zone transfer to the slave box.}}

			[[Category:Networking]]

Jbilyk: update for master/slave

2011-10-06T20:49:15Z

update for master/slave

@@ Line 1: / Line 1: @@
-NSD is an authoritative-only DNS server.  The following page shows how to setup a single-zone configuration.  In the examples 10.1.0.1 is used as the server's IP.  The IP addresses used here (along with the domain) should be replaced with the proper IP addresses of your servers.
+NSD is an authoritative-only DNS server.  The following page shows how to setup a single-zone configuration, with one server being a master where updates are made, and a slave which will have changes replicated to it automatically.  In the examples 10.1.0.1 is used as the master server's IP, while 10.2.0.1 is the slave.  The IP addresses used here (along with the domain) should be replaced with the proper IP addresses of your servers.
 = Install =
@@ Line 25: / Line 25: @@
          name: alpinelinux.org
          zonefile: alpinelinux.org.zone
 </pre>
 Then, create the zone file for the zone in question (/etc/nsd/alpinelinux.org.zone in this case):
@@ Line 68: / Line 70: @@
 build-1-10      IN      A       91.220.88.26
 </pre>
 = Start Server =
-First step, make sure you didn't have any typos in your configuration:
+First step, make sure you didn't have any typos in your configuration (on both boxes):
 {{Cmd|nsd-checkconf /etc/nsd/nsd.conf}}
 Then each time a change is made to the zone (including when you first start the server), you need to rebuild the NSD zone databases:
@@ Line 77: / Line 101: @@
 {{Cmd|/etc/init.d/nsd start
 rc-update add nsd}}

Jbilyk: create page

2011-10-05T22:21:45Z

create page

New page

NSD is an authoritative-only DNS server. The following page shows how to setup a single-zone configuration. In the examples 10.1.0.1 is used as the server's IP. The IP addresses used here (along with the domain) should be replaced with the proper IP addresses of your servers.

= Install =

Installation is simple (perform this step on both servers):
{{Cmd|apk add nsd}}

= Configure =

First, setup the main configuration file on the master server, /etc/nsd/nsd.conf, replacing the secret with a proper one:
<pre>
server:
ip-address: 10.1.0.1
port: 53
server-count: 1
ip4-only: yes
hide-version: yes
identity: ""
zonesdir: "/etc/nsd"
key:
name: "sec_key"
algorithm: hmac-md5
secret: "WhateverSecretYouUse"
zone:
name: alpinelinux.org
zonefile: alpinelinux.org.zone
</pre>
Then, create the zone file for the zone in question (/etc/nsd/alpinelinux.org.zone in this case):
<pre>

;## alpinelinux.org authoritative zone

$ORIGIN alpinelinux.org.
$TTL 86400

@ IN SOA ns1.alpinelinux.org. webmaster.alpinelinux.org. (
2011100501 ; serial
28800 ; refresh
7200 ; retry
86400 ; expire
86400 ; min TTL
)

NS ns1.alpinelinux.org.
MX 10 mail.alpinelinux.org.
lists MX 10 mail.alpinelinux.org.
@ IN A 81.175.82.11
mail IN A 64.56.207.219
www IN A 81.175.82.11
www-prd IN A 74.117.189.132
www-qa IN A 74.117.189.131
wiki IN A 74.117.189.132
lists IN A 64.56.207.219
monitor IN A 213.234.126.133
bugs IN A 81.175.82.11
nl IN A 81.175.82.11
dl-2 IN A 208.74.141.33
dl-3 IN A 74.117.189.132
dl-4 IN A 64.56.207.216
rsync IN A 81.175.82.11
distfiles IN A 91.220.88.29
build-edge IN A 91.220.88.23
build64-edge IN A 204.152.221.26
build-2-2 IN A 91.220.88.34
build64-2-2 IN A 91.220.88.35
build-2-1 IN A 91.220.88.32
build-2-0 IN A 91.220.88.31
build-1-10 IN A 91.220.88.26
</pre>

= Start Server =
First step, make sure you didn't have any typos in your configuration:
{{Cmd|nsd-checkconf /etc/nsd/nsd.conf}}
Then each time a change is made to the zone (including when you first start the server), you need to rebuild the NSD zone databases:
{{Cmd|nsdc rebuild}}
Finally, start the server and set it to auto-start:
{{Cmd|/etc/init.d/nsd start
rc-update add nsd}}