Differences between revisions 13 and 44 (spanning 31 versions)
Revision 13 as of 2017-12-08 23:41:19
Size: 1183
Comment:
Revision 44 as of 2017-12-10 20:03:28
Size: 668
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
= DNS Master = In this setup we use the following IP-addresses for the master and slave:
Line 9: Line 9:
== Network ==  * 192.168.1.34 master
 * 192.168.1.35 slave
Line 11: Line 12:
Since looking up the DNS servers IP-address does not make any sense, we will give the DNS server a statc IP-address. Edit `/etc/networking/interfaces` and make the following changes.

{{{
# The primary network interface
#allow-hotplug eth0
#iface eth0 inet dhcp

auto eth0
iface eth0 inet static
        address 192.168.1.34
        netmask 255.255.255.0
        gateway 192.168.1.1
        network 192.168.1.0
        gateway 192.168.1.1
}}}

== Install BIND ==

{{{
apt-get install bind9
}}}

== Configure BIND ==

Add the new zone file to `/etc/bind/named.conf.local`

{{{
include "/etc/bind/named.conf.kallenberg.dk";
}}}


= DNS Slave =
Configure the [[DNS Master|master]], then the [[DNS Slave|slave]].

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.

None: DNS (last edited 2021-01-17 20:10:16 by Kristian Kallenberg)