Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
DHCP snooping lets a switch decide which ports may answer address requests, blocking rogue servers and building the binding table that two further protections depend on.

What Is DHCP Snooping?
DHCP has no authentication. A client broadcasts a request for an address and accepts the first answer it receives, with no way to tell whether that answer came from the corporate server or from a laptop somebody plugged into a meeting room socket. DHCP snooping is the switch feature that supplies the missing check: ports are classified as trusted or untrusted, and only trusted ports may send server messages. Everything else is dropped before it reaches a client.
A rogue DHCP server hands out addresses with its own machine as the default gateway and as the DNS resolver. Every client that accepts the lease then sends its traffic through the attacker, who is now positioned for a man-in-the-middle attack: reading plaintext, downgrading connections, redirecting name lookups, and collecting credentials. The tooling is ordinary. Responder, Ettercap, and the DHCP modules in common testing distributions do it in one command, and a Raspberry Pi behind a printer is enough hardware.
There is a second, cruder attack. DHCP starvation floods the server with requests using spoofed hardware addresses until the pool is exhausted, so legitimate clients get nothing. It is often used to clear the field before introducing the rogue server. Port security limiting the number of addresses per port, and the DHCP snooping rate limit, both blunt it.
Not every rogue server is hostile. A consumer router plugged in backwards, a virtualisation host with a misconfigured internal network, or a developer’s test environment bridged onto the corporate VLAN will all answer DHCP requests and cause an outage that looks like an attack.
Enable it globally and per VLAN, then mark as trusted only the uplinks towards the real DHCP servers and the links between switches. Every access port stays untrusted by default. On an untrusted port the switch drops DHCPOFFER, DHCPACK, DHCPNAK, and lease query messages, so a rogue server is silenced at the first hop.
While it does this, the switch records every successful lease in the DHCP snooping binding table: the client hardware address, the assigned IP address, the lease time, the VLAN, and the port. That table is the feature’s second and arguably more valuable output, because two other protections read from it.
On Cisco IOS the base configuration is short:
ip dhcp snooping
ip dhcp snooping vlan 10,20,30
no ip dhcp snooping information option
interface GigabitEthernet1/0/48
ip dhcp snooping trust
interface range GigabitEthernet1/0/1-47
ip dhcp snooping limit rate 15
Three points cause most of the trouble. Option 82, the relay agent information option, is inserted by the switch and then rejected by many servers that are not configured to expect it; disable insertion or configure the server to trust it. The binding table is lost on reboot unless you write it to flash or a remote location, and losing it breaks Dynamic ARP Inspection for clients with existing leases. And static addresses need manual bindings or an ARP access list, or those hosts stop working the moment you enable inspection.
Roll it out in stages. Enable snooping first and watch for drops on ports you expected to be quiet. Only once the binding table is stable should you turn on Dynamic ARP Inspection and IP Source Guard, and do it VLAN by VLAN. Equivalent features exist on HPE Aruba, Juniper, and Extreme platforms under similar names, so a mixed estate can be covered consistently.
Layer-two hardening of this kind pairs naturally with 802.1X and VLAN hardening; together they close most of the attacks available to someone who gets physical access to a socket. Our Infrastructure and Architecture Review Services check these settings across the switching estate rather than on a sample.
Only the ports facing your legitimate DHCP servers and the inter-switch links that carry server traffic. Every access port where users, phones, printers, or wireless access points connect should remain untrusted. A common mistake is trusting an entire uplink range for convenience, which reintroduces the risk wherever that range reaches a user-accessible area.
Only if the wireless traffic passes through a switch port where snooping is applied, and only for the rogue server case. Most wireless controllers have their own equivalent protections, including client isolation and DHCP server validation, which should be enabled separately. Treat the wired and wireless controls as two configurations that must both be checked.
They never appear in the binding table because they never request a lease. DHCP snooping alone does not affect them, but Dynamic ARP Inspection and IP Source Guard will block them once enabled. Create static bindings or an ARP access list for servers, printers, and network equipment with fixed addresses before turning those features on.
Not for the rogue server attack on a correctly configured switch, since server messages are dropped at the port. The practical bypasses involve configuration gaps: a VLAN where snooping was never enabled, an access port mistakenly marked trusted, or a switch in the path that does not support the feature. Audit the whole layer-two path, not just the edge switch.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.