|
Size: 911
Comment:
|
Size: 886
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| == Network == | In this setup we use the following IP-addresses for the master and slave: |
| Line 9: | Line 9: |
| Since looking up the DNS servers IP-address does not make any sense, we will give the DNS server a statc IP-address. | * 192.168.1.34 master * 192.168.1.35 slave |
| Line 11: | Line 12: |
| /etc/networking/interfaces | Configure the [[DNS Master|master]], then the [[DNS Slave|slave]]. |
| Line 13: | Line 14: |
| {{{ # The primary network interface #allow-hotplug eth0 #iface eth0 inet dhcp |
== Maintenance == |
| Line 18: | Line 16: |
| auto eth0 iface eth0 inet static address 192.168.1.34 netmask 255.255.255.0 gateway 192.168.1.1 }}} |
=== DNS changes === |
| Line 25: | Line 18: |
| == Install BIND == {{{ apt-get install bind }}} |
Once both servers are configured, it is vital to stop making changes to the zone files by hand. From now on DNS changes has to be made with nsupdate using the update key. |
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 DNS changes has to be made with nsupdate using the update key.