Differences between revisions 4 and 53 (spanning 49 versions)

DNS

The Domain Name System is really a must for any TCIP/IP network. It is a key component of the network. That is why it is the first service we will configure.

Here we will be using Bind, ISC's DNS server. Bind has a master/slave configuration, where the master gets the DNS changes and then updates the slave. It cannot run truly redundant, in the sense that only the master is allowed to get DNS changes, if the master is down, the slave cannot be updated.

In this setup we use the following IP-addresses for the master and slave:

192.168.1.34 master
192.168.1.35 slave

Configure the master, then the slave.

Maintenance

Zone Changes

Once both servers are configured, it is vital to stop making changes to the zone files by hand. From now on manual DNS updates has to be made with the nsupdate utility using the update key. If you try to edit the zone files manually, you may be screwing up your DNS.

-  ⇤ ← Revision 4 as of 2017-12-08 15:47:43 → 
  Size: 524
  Editor: Kristian Kallenberg
  Comment:
+   ← Revision 53 as of 2017-12-13 10:03:56 → ⇥
  Size: 1001
  Editor: Kristian Kallenberg
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 7:
-== Domain ==
+In this setup we use the following IP-addresses for the master and slave:
 Line 9:
-=== Memory ===
128M
+ * 192.168.1.34 master
 * 192.168.1.35 slave
 Line 12:
-== OS ==
+Configure the [[DNS Master|master]], then the [[DNS Slave|slave]].

== Maintenance ==

=== Zone Changes ===

Once both servers are configured, it is vital to stop making changes to the zone files by hand. From now on manual [[DNS Updates|DNS updates]] has to be made with the `nsupdate` utility using the update key. If you try to edit the zone files manually, you may be screwing up your DNS.