diagram
|
|
| A solution for beginners or for people who do not have multiple servers available to them. This solution includes a single physical server running 2 instances of Tinydns. The end result is the ability to have 2 nameservers, thus meeting the registrar requirements for delegating domains to your DNS system. This solution offers almost no redundancy in case of server failure, but is a good start for beginners or for the financially challenged. |
|
diagram
|
|
| A fully redundant, professional solution suitable for controlling DNS for large numbers of domains. A physical master server backed up by 2 or more physical slave servers ensures full and instant redundancy should one or more servers go down for any reason. Changes are made to domain records on the master server and within minutes the 2 or more slave servers remotely sync with the master server, resulting in multiple servers containing the exact same DNS records. This solution requires at least 3 physical servers. |
|
| 1. Getting started - Requirements and pre-requisites. |
1. Getting started - Requirements and pre-requisites. |
| 2. Download - Get the needed djbdns software. |
2. Download - Get the needed djbdns software. |
| 3. Installing djbdns itself - The foundation for it all |
3. Installing djbdns itself - The foundation for it all |
| 4. Deploying tinydns - The DNS sevrver itself |
4. Deploying tinydns - The DNS sevrver itself |
| 5. DNScache - Deploying a local DNS cache |
5. DNScache - Deploying a local DNS cache |
| 6. Deploying Vegadns - A web based DNS interface |
6. Deploying Vegadns - A web based DNS interface |
| 7. Test drive - Testing your new DNS server |
7. Fun with rsync- Syncing all of your servers. |
| 8. Under the hood - A look behind the scenes. |
8. Test drive - Testing your new DNS server |
| 9. Expansion - Upgrading to multiple servers. |
9. Under the hood - A look behind the scenes. |
| 10. Closing notes & feedback |
10. Expansion - How to add additional slave servers. |
| |
11. Closing notes & feedback |
