Researching of Dynamic Host Configuration Protocol Essay

Disadvantages of Dynamic Host Configuration Protocol (DHCP)

DHCP automation poses a security risk in the event of a rogue DHCP server getting introduced into the network. The network personnel would not have control of a rogue network that could provide IP addresses to those connecting to the network. In addition, users connected to the rogue DHCP can have their information intercepted when using the rogue DHCP. A rogue DHCP can be solved by troubleshooting, using a network sniffer, looking into sFlow data, or Syslog tools. Prevention is achieved by checking for misconfigured and conflicting IP addresses.

Another problem with DHCP is a single point of failure if only one DHCP server is operational. This issue forms a junction where one issue can cascade into system-wide problems causing connected computers to try and fail at obtaining IP addresses. This problem is addressed by using failover clustering, split scopes, or standby servers.

Another problem with DHCP is its packets cannot travel across routers. This issue necessitates a relay agent that enables the server to handle leases on both network segments. A relay agent receives broadcast packets forwarding them as unicast to the DHCP server. This problem has long been addressed through a relay agent.

How to Configure a DNS Server on a Network Server on Windows Server 2016

1. Proceed to ‘local server’ after opening the Server Manager window
2. Click manage and then ‘Add Roles and Features.’
3. On the add other roles wizard that appears, read the information provided in the ‘Before you Begin’ and then click Next.
4. Select the radio button for the option you want; in this case, select the assumption that is Role-based or Feature-based installation.
5. For a typical DNS server, the server for the specific role is on the same machine one is working on, but remote installation is also available.
6. Pick the DNS Server Role
7. A window will display asking to confirm dependencies to be installed (these are usually the Administrative Tools that the DNS role requires. Finally, click on Add Features since it is generally required.
8. There should be a black check icon that is marked, then click Next.
9. One can install additional features in the features window typically not needed to configure the DNS-only but might be required later.
10. The following window will describe services and functions stipulating the effects of the role of the requirements.
11. The final step is to confirm the installation to restart the server, and then it returns to the server manager window.

The Future of DNS

The Domain Name System (DNS) is decades-old technology integrated into virtually every aspect of web infrastructure. The system is ubiquitous, and any proposal at phasing it out seems almost futile; a more realistic approach is for it to evolve, as has been the case since its inception. One area that will radically affect the DNS system is the idea of the Internet of Things. It is a legitimate concern whether DNS can sufficiently provide a naming system for a ubiquitous IoT. An already implemented solution includes IPv6 with a 2¹²⁸ namespace that would be enough to power the IoT and Internet of Everything (IoE). Some proposals are to develop a system based on the DNS system, while others propose a clean slate system. Important considerations for a future system include security, infrastructure dependence, mobility, localization, and efficiency.