I  think  the  DHCP  Starvation  Attacks  means ,  Its  an inability  of  DHCP  Server  to  give  an  IP  Address  to   machine,  Because  the  fake  user  allocate  all  IP  address  from  the  Server  by  Sending  the  Continuous  DHCP  request  to  Server. Then  the  DHCP  Server  running  out  of  IP's.    We  can  prevent  this  attack   by   put  MAC  Learn limit in  Server  Machine Port.. Port security allows you to specify MAC addresses for each port or to permit a limited number of MAC addresses.

As already mentioned: Properly configured "Port security"  is a countermeasure against DHCP starvation.

Cisco switches  allow for so called "DHCP snooping": It is possible to specify trusted and untrusted ports. The trusted port should be the port where the DHCP server is connected to. The switch does not allow any DHCP responses (offer, ack)  on untrusted ports. For an introduction seee here: http://packetpushers.net/ccnp-studies-configuring-dhcp-snooping/

For e.g. Cisco Nexus 7000 series you can find the details here: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/4_1/nx-os/security/configuration/guide/sec_nx-os-cfg/sec_dhcpsnoop.html

I only know Cisco networking devices; but I assume other manufacturers have similar technologies…

Besides the port security mentioned, also DHCP snooping can be applied on switches in relatively easy way that helps a lot. In cad that Nikhil finds a solution solely on the server (that is not the case of port security and DHPC snooping requiring switches with the support of these features), the manual pre-registration of MAC addresses of allowed devices before their first connection into the network could be a solution but it is a bit boring and hefty.

The problem with port security is if we are using shared networks like wireless medium (access points), we can't make use of port security because it is limited to switches.