|
Size: 710
Comment:
|
Size: 1001
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: |
| {{{ . }}} |
== Maintenance == |
| Line 17: | Line 16: |
| == Install BIND == | === Zone Changes === |
| Line 19: | Line 18: |
| {{{ 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 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. |
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.