DHCP&_160;· DNS&_160;· FTP&_160;· Gopher&_160;· HTTP&_160;· IMAP4&_160;· IRC&_160;· NNTP&_160;· XMPP&_160;· POP3&_160;· RTP&_160;· SIP&_160;· SMTP&_160;· SNMP&_160;· SSH&_160;· TELNET&_160;· RPC&_160;· RTCP&_160;· RTSP&_160;· TLS (and SSL)&_160;· SDP&_160;· SOAP&_160;· GTP&_160;· STUN&_160;· NTP&_160;· BGP&_160;· RIP&_160;· (more)Dynamic Host Configuration Protocol is a way to manage network parameter assignment from a single DHCP server, or a group of DHCP servers arranged in a fault-tolerant manner. Even in small networks, Dynamic Host Configuration Protocol is useful because it can make it easy to add new machines to the local network.
DHCP is also recommended even in the case of servers whose addresses rarely change, so that if a server needs to be readdressed (RFC2071), changes can be made in as few places as possible. For devices such as routers and firewalls, that should not use DHCP, it can be useful to put Trivial File Transfer Protocol (TFTP) or SSH servers on the same machine that runs DHCP, which also serves to centralize administration.
DHCP can be used to assign addresses directly to servers and desktop machines, and, through a Point-to-Point Protocol (PPP) proxy, to dialup and broadband on-demand hosts, as well as for residential Network address translation (NAT) gateways and routers. DHCP is generally not appropriate for infrastructure such as non-edge routers and DNS servers.
