Differences between revisions 3 and 50 (spanning 47 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

DNS 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 try to edit the zone files manually, you may be screwing up your DNS.

-  ⇤ ← Revision 3 as of 2017-12-08 15:36:56 → 
  Size: 472
  Editor: Kristian Kallenberg
  Comment:
+   ← Revision 50 as of 2017-12-13 09:56:26 → ⇥
  Size: 996
  Editor: Kristian Kallenberg
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 6:
+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 [[DNS Master|master]], then the [[DNS Slave|slave]].

== Maintenance ==

=== DNS 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 try to edit the zone files manually, you may be screwing up your DNS.