Static & Default Routing
Static and default routing is how you hand a Cisco router explicit, administrator-defined paths to remote networks — the foundational routing skill every CCNA candidate has to own before touching a dynamic protocol. This hub gathers the concept map, step-by-step guides, a command cheat sheet, and graded hands-on labs so you can go from reading a routing table to building resilient backup paths.
New to this? Start with the explainer: How Does Routing Work? The Routing Table Explained
Static routing means you manually tell the router how to reach a network instead of letting a protocol like OSPF or EIGRP learn it dynamically. It sits in the IP connectivity domain of the CCNA blueprint (exact exam weightings shift between blueprint revisions, so treat any percentage as approximate) because it is the clearest way to see how the routing table is actually built and consulted, and because production networks genuinely rely on static and default routes at stub sites, WAN edges, and the path toward the internet. A static route carries a default administrative distance of 1, so the router trusts it over nearly every dynamic protocol.
The first fork to understand is next-hop versus exit-interface. A static route can point at a next-hop IP address, an exit interface, or both. A next-hop route triggers a recursive lookup: the router first finds the route to the next-hop address, then resolves how to actually reach it. An exit-interface route skips that recursion but, on a multi-access segment like Ethernet, depends on proxy ARP to resolve the far end; on a true point-to-point link it works cleanly. That trade-off is exactly what the 'How to Configure a Static Route on Cisco' guide walks through command by command.
The default route (0.0.0.0/0) is a special static route that matches any destination not found by a more specific entry — the 'when in doubt, send it here' path. Once installed it becomes the gateway of last resort and appears in the table with the code S*. This is the pattern you use to point a branch or home network toward an upstream ISP. The 'How to Configure a Default Route (Gateway of Last Resort)' guide covers the syntax and how to confirm the gateway of last resort is actually set.
For resilience, a floating static route is a backup you install with a deliberately higher administrative distance than the primary path. Because IOS prefers the lowest administrative distance, the floating route stays dormant, out of the routing table, and only takes over when the primary route disappears. It is the simplest form of failover — commonly a static backup behind a dynamic-routing primary, or a secondary WAN link behind the main one.
All of this is verified by reading the routing table with show ip route. Learn the codes — C for a connected network, L for the local /32 interface address, S for a static route, and S* for the candidate default — along with how the gateway-of-last-resort line reports. Being able to read the table fluently is what turns configuration into troubleshooting, and it is a skill every later topic (OSPF, EIGRP, redistribution) builds on.
Master the topic in three passes. First, understand the concepts mapped here so you know why each route type behaves the way it does. Second, keep the Static & Default Routing Cheat Sheet open for exact command syntax while you work. Third, prove it in the graded labs and bundle, where you build these routes on a real Cisco IOS CLI and get immediate pass/fail feedback rather than guessing. Understand, reference, then build and grade — that loop is what makes the commands stick.
Step-by-step guides
Follow these to configure it yourself, command by command.
- How to Configure a Static Route on Cisco (Step by Step)Configure static routes on Cisco IOS correctly: next-hop vs exit-interface, administrative distance, floating static backups, and how to verify they install.
- How to Configure a Default Route on Cisco (Gateway of Last Resort)Configure a static default route on Cisco IOS, confirm the gateway of last resort, originate it into OSPF, and add a floating static backup.
Command cheat sheet
Practice on real Cisco IOS
Build and grade hands-on Cisco Modeling Labs — the only way it sticks.
Frequently asked questions
What's the difference between a next-hop and an exit-interface static route?
A next-hop static route (ip route <network> <mask> <next-hop-ip>) triggers a recursive lookup: the router resolves the next-hop address against the rest of its table to learn how to forward the packet. An exit-interface route (ip route <network> <mask> <interface>) avoids recursion but relies on proxy ARP on multi-access media such as Ethernet, so a common best practice there is to specify both the exit interface and the next-hop IP. Either way, the route carries a default administrative distance of 1.
What is a floating static route and how do I create one?
A floating static route is a backup path configured with an administrative distance higher than the route it protects — you add the distance value at the end of the ip route command. Because IOS installs the route with the lowest administrative distance, the floating route stays out of the routing table until the primary path fails, then takes over automatically. Choose a value above the primary's administrative distance (for example, higher than 110 if you are backing up an OSPF-learned route).
In what order should I learn static, default, and floating routes?
Start by reading the routing table (show ip route and its codes), then configure a basic static route, then a default route / gateway of last resort, and finally floating static routes for redundancy. That progression matches the CCNA IP-connectivity flow and the order of the guides in this hub, and it gives you the table-reading foundation that dynamic protocols like OSPF and EIGRP build on next.
Study every CCNA topic this way
The CCNA Complete Path sequences all 17 lab bundles into one graded progression you own forever.