AD DC and DNS Redundancy - VBychkov-boop/Spring-SYS265-Final-Project GitHub Wiki

Redundancy:

Redundancy in a network means having backup systems in place so that if one component fails, another takes over automatically, keeping everything running without interruption. Just like you wouldn't rely on a single key to access your home, you shouldn't rely on a single server, connection, or device to keep your network running. Without it, one failure could bring down your entire network, stopping users from logging in, accessing files, or doing their jobs costing the organization time and money. To this end we have created redundant systems for three vital points of the network, the AD DC, DNS, and DHCP servers.

AD DC:

The creation of the Redundant AD DC server was largely comprised of two important steps configuring the dc02 device and adding/escalating it in the server manager.

• Configuring the dc02 device involved setting the network settings of the device, setting the DNS servers, and adding it to the Domain.

• adding the device to the server manager on mgmt01 involved searching the domain for the device, adding it as a server via the "add server" function. Once the device is added a server, use the add roles and features function to add the AD DC role and management tools. Once this installation is complete check the yellow flag at the top of the screen and click "escalate to domain controller". Once you have escalated the server it should be functional as a redundant AD DS server.

DNS:

The creation of the redundant DNS follows the creation of the redundant AD DC; there is only one major step and that is the installation of the DNS service onto the dc02 Server.

• use the add roles and features function to add the DNS role. Once this installation is complete check the yellow flag at the top of the screen and enable the DNS, set the DSRM Password and set it to copy the main DNS server.