Controlling the DHCP database on a DHCP server will help you determine which DHCP clients are receiving the address directly from the server better. In addition, this process also helps you identify BAD_ADDRESS components in the database, and where they came from … these information are really useful, when they can cause conflicting addresses when The fake DHCP server system performs address assignment while they are still in use.
Unfortunately, problems related to DHCP security are often difficult to resolve and resolve. There is no authentication or signal recognition process between the exchange of data between the DHCP server and the DCHP client, so the server system cannot know whether the signal sent from the client is safe on the whole. Network system, and vice versa, the client also cannot know whether the signal returned from the server is safe enough. The ability to fake signals from the client and server can cause unpredictable results.
For example, a fake DHCP server can provide legitimate clients with completely bogus TCP / IP information, and thereby prevent the victim from communicating with other clients in the system. And then, the Denial Of Service (DoS) process will make all users unable to connect to the network, as well as all shared resources. Setting up and distributing fake DHCP server signals is as simple as a social network attack, or you can connect to a laptop and adjust and configure it like a normal DHCP server.
Another situation that could easily be encountered regarding attackers will affect the client computer on the network, and thereby install continuous software that requires new IP addresses to use the mechanism. The MAC spoofs until the entire address is allocated in the full DHCP server system. When this situation occurs, all legitimate clients cannot boot on the network due to unrecognized and allocated addresses, and of course, users cannot access the resource system. and work.
On Windows networks, DHCP and DNS can work together to simplify the process of setting up and customizing network system operations. Usually, the most common problem is that the DHCP client registers a direct (host) record with the DNS server, while the pointer PTR is registered instead of the client by the DHCP server. This means that attacks on DHCP servers can control through logs registered with the DNS server system and continue to be used to redirect traffic to bad websites, or to cause problems. Denial Of Service – DoS. If you “turn” the DHCP server into a member of the DNSUpdateProxy group, your DHCP server will not lose ownership or data records of the client. These are mostly used when updating or upgrading from Windows NT to ensure that subordinate clients that do not support DNS can lose their ownership when upgrading to Windows 2000 or Windows XP.