dhcp
Home > IT Answers > Networking > dhcp
Rajpandey
40 pts.
0
Q:
dhcp
DHCP
what is the drawback of dhcp?
ASKED: Jun 26 2009  4:42 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
Labnuke99
26290 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
It is hard to think of any real drawbacks. Generally it is not configured to allocate the same IP address to the same device, but this can be done, so it can even be used for devices such as network printers. Although it is usually considered good practice to configure the address on the device itself rather than use DHCP. I suppose that DHCP servers could be faked by someone wanting to disrupt the network, but that is not a hugely likely event. A possible drawback is that it requires some knowledge of how to configure it to work correctly, and how to configure routers to pass the DHCP requests to the server when the client is on a different subnet.

Overall I would say that the benefits vastly outweigh the drawbacks (which are few).

But I am sure there is some good mileage in this discussion :-)

=================
DHCP is a broadcast protocol. When a client asks for IP address info, all systems have to process the packet. So if the lease duration is set to a very short time, the network could become flooded by DHCP request broadcasts. The challenge with DHCP is address to name resolution. This means that DHCP cannot stand alone without dynamic DNS. Not all DHCP is created the same.

Yes, rogue DHCP could be a real issue if someone wanted to publish a malicious DNS server for client name resolution. The DNS server could resolve microsoft.com to malwaresoftware.com or something. A rogue DHCP server could even pass out bad network information and cause clients to not be on the same subnet as company resources. I have seen this happen if someone brings in a rogue wireless access point with DHCP on the LAN side handing out a 192.168.x.x subnet when the clients should be on a company subnet. This caused the clients who got addresses from this rogue DHCP server to "lose connectivity" with the resources they needed to access. This could be considered a denial of service (DOS) attack.

In the IT trenches? So am I - read my IT-Trenches blog
Last Answered: Jun 26 2009  12:06 AM GMT by Labnuke99   26290 pts.
Latest Contributors: BlankReg   11280 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Robert Stewart   1810 pts.  |   Jun 26 2009  4:23PM GMT

The biggest drawback would be DHCP are leased IP’s and subject to change, this is a problem if you want to network stuff together, machines need to know that certain devices can always be reached at certain IP’s, such as servers, network printers, network storage etc. etc. Other than that there are benefits to both static and dynamic ips.

 

Snapper70   540 pts.  |   Jun 26 2009  7:00PM GMT

Typically, assign fixed resources (i.e. printers, servers, network equipment) fixed addresses; and let all the client machines (laptops / desktops / movile devices) use DHCP. Just remember to set up your DHCP scope(s) to stay away from these fixed-resource address ranges.

 

Technochic   40210 pts.  |   Jun 29 2009  4:15PM GMT

Reserving addresses in DHCP for static IP’s is also helpful so if the device with a reserved IP goes off-line no other device will pick up that IP.

 

Rklanke   750 pts.  |   Aug 4 2009  6:30PM GMT

Assuming that DHCP is in charge is a drawback. People tend to forget that local IP configuration settings override the settings DHCP delivers. If you that you were managing IP configurations by managing DHCP … well, no. Anyone who thinks they know better can explicitly specify their own IP address, DNS server or list of domains (for example).

 
0