# Designated Router

> Source: Courseiva IT Certification Glossary — https://courseiva.com/glossary/designated-router

## Quick definition

In OSPF, a Designated Router is a router chosen by other routers on the same network segment to act as a central point for exchanging routing information. This router collects updates from all neighbors and sends a single summary to everyone, making the process efficient. It also helps in forming neighbor relationships and reduces the number of routing updates that need to be flooded.

## Simple meaning

Think of a Designated Router as the team leader in a group project where everyone needs to share information. In a network, many routers might be connected to the same switch, and if every router had to talk to every other router directly, the amount of messages would become overwhelming. This is especially true in large networks like those found in companies or data centers.

Instead of each router sending updates to every other router, they elect one router to be the Designated Router, or DR. This DR collects all the routing information from everyone on that network segment. After gathering all the details, the DR then sends out a single, consolidated update to all the other routers. This way, each router only has to talk to the DR and one other special router called the Backup Designated Router, which takes over if the DR fails. This cuts down on traffic and helps the network stay stable and responsive.

In everyday terms, imagine a busy office where ten people are working on the same project. If every person had to tell every other person their progress, it would lead to chaos and wasted time. Instead, they appoint one person as the coordinator. Everyone reports their progress to the coordinator, and the coordinator then sends a single newsletter to the whole team. If the coordinator is sick, a backup person takes over, and the workflow continues smoothly. That is exactly how a Designated Router works in an OSPF network.

The DR is only needed on certain types of network connections, specifically those where multiple routers can talk to each other directly, like over an Ethernet switch. For point-to-point links, where only two routers are connected, there is no need for a DR because there is no congestion of messages. The DR election process is automatic and uses priorities and router IDs to determine who becomes the DR. It is a simple yet powerful mechanism that makes large networks run efficiently.

## Technical definition

In Open Shortest Path First (OSPF) protocol, a Designated Router (DR) is a critical entity defined in RFC 2328 for operation on broadcast and Non-Broadcast Multi-Access (NBMA) networks. OSPF is a link-state routing protocol that builds a complete topology map of the network by exchanging Link State Advertisements (LSAs) among routers. On multi-access networks such as Ethernet, where more than two routers can connect to the same Layer 2 segment, the default flooding mechanism would cause each router to form an adjacency with every other router. This results in an O(n²) explosion of adjacencies, which in turn creates excessive LSA flooding and increases CPU and memory overhead on all participating routers.

The DR solves this scalability problem by becoming the central point for LSA exchange. All other routers on the segment form a full adjacency only with the DR and a Backup Designated Router (BDR). These routers are said to be in a full state only with the DR and BDR. Neighbors that are not DR or BDR remain in a 2-way state with each other and do not exchange LSAs directly. This reduces the total number of adjacencies from n(n-1)/2 to 2n-2, a significant reduction in large networks.

The election of the DR and BDR is deterministic and based on two parameters: the OSPF priority (a configurable value from 0 to 255) and the Router ID (RID), which is typically the highest IP address on a loopback interface or the highest active physical interface IP. A router with priority 0 never participates in the election and can never become DR or BDR. The election algorithm is as follows: the router with the highest priority becomes the DR. If there is a tie, the router with the highest RID wins. The router with the second highest priority becomes the BDR. Once elected, the DR remains in its role until it fails, even if a router with a higher priority joins the network later. This is a non-preemptive election to ensure stability.

On broadcast networks like Ethernet, OSPF uses multicast addresses to communicate: 224.0.0.5 for all OSPF routers and 224.0.0.6 for DR/BDR traffic. All routers send LSAs to the DR and BDR on multicast 224.0.0.6. The DR then flushes these LSAs to all other routers on multicast 224.0.0.5. This efficient use of multicast reduces traffic and avoids unnecessary processing on non-DR routers.

On NBMA networks like Frame Relay or ATM, OSPF can operate in point-to-point, point-to-multipoint, or NBMA mode. In NBMA mode, the DR concept is still used, but routers communicate via unicast instead of multicast because the underlying network does not support broadcast. Manual configuration of neighbors is often required in these environments.

The Backup Designated Router (BDR) serves as a hot standby. It also forms full adjacencies with all routers and receives the same LSAs as the DR. If the DR fails, the BDR immediately takes over without requiring a new election. This minimizes network disruption. While the BDR is active, it does not generate its own LSAs; it simply listens and remains ready.

Real IT implementations often involve tuning the OSPF priority to control which router becomes the DR. For example, a network administrator might set a high priority on a router with more CPU or memory resources to ensure it handles the DR workload. Conversely, a router with limited resources might be set to priority 0 to avoid election entirely. In modern data center networks, the DR concept still applies, though protocols like OSPFv3 for IPv6 use the same election mechanism with Router ID based on IPv4 addresses.

Understanding the DR is essential for OSPF troubleshooting. Common issues include DR election conflicts due to misconfigured priorities, routers not becoming neighbors because they do not see the DR, or LSAs not being flooded correctly if the DR fails and the BDR is not properly synchronized. Tools like 'show ip ospf neighbor' and 'show ip ospf interface' are used to verify DR/BDR roles and adjacency states.

## Real-life example

Imagine you are organizing a large community potluck dinner where 30 families are bringing different dishes. If every family had to talk directly to every other family to coordinate what dish to bring, it would be absolute chaos. There would be hundreds of phone calls, repeated information, and mistakes. Instead, the group elects one organizer (the DR) and a backup organizer (the BDR). Each family calls only the organizer and tells them what they are bringing. The organizer writes it all down and then sends a single list to everyone. This saves time and ensures everybody knows the plan. If the organizer gets sick, the backup steps in immediately without needing a new vote.

Now map this to the OSPF network. The families are the routers on an Ethernet segment. The potluck dishes are the routing updates (LSAs). The organizer is the Designated Router, and the backup is the Backup Designated Router. Without the DR, each router would need to exchange LSAs with every other router, creating a mesh of connections that would overwhelm the network with chatter. With the DR, each router only speaks with the DR and BDR, drastically cutting down on overhead.

Consider a real-world scenario: a university campus with dozens of routers all connected to a core switch. Without a DR, the OSPF traffic would be enormous, causing slow convergence and higher CPU usage on every router. The network team configures OSPF priorities on the most capable router to become the DR. That router handles all LSA flooding. When a new building is added, its router simply forms an adjacency with the DR. The rest of the network learns about the change from the DR’s single update. This is efficient and stable.

In another analogy, think of a sports team. The DR is like the captain who talks to the coach and then relays the game plan to the rest of the team. The BDR is the vice-captain who knows the plan and can take over if the captain is injured. The other players (routers) only need to listen to the captain and vice-captain; they don't need to talk strategy directly with every teammate. This analogy holds because in OSPF, non-DR routers never exchange LSAs directly with each other on the same segment.

## Why it matters

In practical IT environments, the Designated Router concept is vital for network stability and performance. When you manage a network with multiple routers on the same switch, OSPF without a DR would generate massive amounts of routing traffic. Every link-state change, such as a link going down or a new route being added, would be flooded to every router individually. This consumes bandwidth and CPU cycles on all devices, potentially causing network sluggishness or even failure during convergence.

The DR reduces this burden by centralizing the flooding process. This is especially important in data centers and enterprise networks where hundreds of routers may exist on a single VLAN. By electing a DR, the network ensures that only one router (the DR) is responsible for disseminating LSAs. This makes OSPF scalable and efficient.

From a troubleshooting perspective, understanding the DR is crucial. If a router is not forming full adjacencies, the issue might be related to DR election. For instance, if two routers both have priority 0, they will never become DR/BDR, and they will remain in 2-way state. Or if a higher priority router joins after the election, it will not preempt the existing DR, which can surprise administrators who expect the new router to take over. Knowledge of non-preemptive behavior is key.

In certification exams like CCNA and Network+, questions about DR often appear in the context of OSPF configuration and troubleshooting. Being able to interpret 'show ip ospf neighbor' output to identify DR and BDR is a common skill tested. For cloud exams like AWS SAA and AZ-104, the concept translates to understanding how routing protocols work in virtual private clouds and hybrid networks. Even if you do not configure OSPF directly in AWS, knowing how DR works helps you understand network architecture and troubleshooting connectivity issues.

The DR concept also affects network design decisions. For example, in a hub-and-spoke topology, the hub router is a natural candidate for DR due to its central role. Misconfiguration can lead to suboptimal traffic patterns or failure to converge after a link failure. Therefore, every network professional should have a solid grasp of DR and BDR roles.

## Why it matters in exams

The Designated Router is a core topic in several major IT certification exams, particularly those focusing on networking. For the CCNA exam (Cisco Certified Network Associate), OSPF is a major part of the curriculum. You will be expected to know how DR and BDR election works, the commands to view and verify DR/BDR status, and how to configure OSPF priority. Questions may ask you to identify the DR based on given Router IDs and priorities, or to choose the correct statement about OSPF adjacency on a multi-access network. The CCNA often includes scenario-based questions where you must troubleshoot why a router is not becoming full adjacency, and the answer could involve DR election issues.

For the CompTIA Network+ exam, OSPF is covered at a conceptual level. While you won't be required to know detailed configuration commands, you must understand that OSPF uses a Designated Router to reduce traffic on broadcast networks. The exam might present a question asking which protocol employs a DR to improve efficiency, or what mechanism OSPF uses to minimize link-state updates. Understanding DR is also relevant to the objective of comparing routing protocols.

The AWS Certified Solutions Architect Associate (SAA) exam does not directly test OSPF configuration, but it tests understanding of hybrid networking. For example, when using AWS Direct Connect or VPN connections, on-premises routers may run OSPF with AWS virtual private gateways. In such setups, the DR concept applies to the on-premises side. A question about BGP vs OSPF may include a distractor about DR. The AWS Advanced Networking Specialty exam, which is more specialized, includes OSPF and DR details.

For the Microsoft Azure AZ-104 exam, OSPF is not a major focus, but you should know that Azure VPN gateways support BGP and static routing, and OSPF is used in some hybrid scenarios. Understanding DR helps you grasp why certain routing behaviors occur. The Google Associate Cloud Engineer exam also touches on hybrid connectivity where OSPF may be used.

The CompTIA Security+ and A+ exams are lighter on routing protocols, but they still might have a question about network segmentation or protocols. DR is not a core objective, but general network knowledge helps. Overall, for CCNA and Network+, DR is an essential topic. For cloud certifications, it is supportive knowledge.

Exam questions might ask: Which router becomes the DR on an OSPF network with priorities 100, 50, and 0, and Router IDs 1.1.1.1, 2.2.2.2, and 3.3.3.3? The answer is the one with the highest priority (100), and if a tie, the highest RID. Another common question: What multicast address do OSPF routers use to send updates to the DR? The answer is 224.0.0.6. Know these details well.

## How it appears in exam questions

Designated Router questions typically fall into three categories: scenario-based, configuration-based, and troubleshooting-based. In scenario-based questions, you are given a network diagram with several routers connected to a switch. You are asked to determine which router will become the DR and which will become the BDR based on provided priorities and Router IDs. For example: R1 priority 200, RID 192.168.1.1; R2 priority 200, RID 192.168.2.1; R3 priority 100, RID 192.168.3.1. The correct answer is R2 becomes DR because it ties on priority but has higher RID, R1 becomes BDR, and R3 is DROTHER.

Configuration-based questions ask you to choose the correct command to set the OSPF priority on an interface, such as 'ip ospf priority 50' in interface configuration mode. They may also ask which interface configuration prevents a router from becoming DR (setting priority to 0). Another variation: What is the effect of changing the priority after election? The answer is that it has no immediate effect because the election is non-preemptive.

Troubleshooting questions present a show command output. For example, 'show ip ospf neighbor' might list neighbors in 2WAY/DROTHER state. The question asks why full adjacency is not formed. The answer is that on a multi-access network, routers only go to full state with DR and BDR, so DROTHER routers remain in 2-way state. Another troubleshooting scenario: A new router with high priority is added, but it does not become DR. The question asks why. The answer is that the DR election is non-preemptive; the existing DR remains until it fails.

Questions also appear in the context of OSPF network types. For instance, on a point-to-point link, there is no DR election. A question might ask which OSPF network type does not use DR/BDR. The correct answers are point-to-point and point-to-multipoint. For NBMA networks, DR election still occurs but requires manual neighbor configuration. You might see a question about the multicast addresses: which address do non-DR routers use to send LSAs to the DR? Answer: 224.0.0.6.

Finally, exam questions sometimes mix DR with BGP or other protocols. For example, a question may ask which protocol uses a designated router concept. The answer is OSPF (as opposed to EIGRP or BGP). Some questions ask about the purpose: why does OSPF elect a DR? To reduce the number of adjacencies and LSA flooding on multi-access networks. Be prepared for all these formats.

## Example scenario

You are a network administrator for a mid-sized company. You have three routers connected to the same Ethernet switch: R1, R2, and R3. You have just configured OSPF on all three. R1 has a priority of 10 and a Router ID of 10.0.0.1. R2 has a priority of 5 and a Router ID of 10.0.0.2. R3 has a priority of 10 and a Router ID of 10.0.0.3. You check the OSPF neighbors after a few minutes and see that R1 and R3 are in FULL state with each other, but R2 is only in 2WAY state with both. Why?

The answer lies in the DR election. R1 and R3 both have priority 10, so they tie. The tiebreaker is the highest Router ID, which is 10.0.0.3 (R3). So R3 becomes the Designated Router. The next highest priority is R1 with 10.0.0.1, so R1 becomes the Backup Designated Router. R2 has a lower priority (5) and becomes a DROTHER. On an OSPF multi-access network, DROTHER routers only form full adjacencies with the DR and BDR. R2 forms full adjacency with R3 (DR) and R1 (BDR). R2 does not form full adjacency with another DROTHER, so it remains in 2WAY state.

Now imagine that R3 (the DR) fails. R1, as the BDR, immediately takes over as the new DR. A new BDR election occurs among the remaining routers. R2 now has the highest priority among the remaining, so it becomes the new BDR. This transition happens quickly, and network convergence is smooth because the BDR was already synchronized with all routers. Without the DR/BDR mechanism, the failure of one router would require all routers to re-establish adjacencies with each other, causing significant network disruption.

This scenario is typical of a real-world network. Understanding this process helps you predict network behavior and troubleshoot issues when adjacencies do not form as expected. If you see a router stuck in 2WAY state, it is not a problem on a multi-access network; it is the expected behavior.

## Designated Router Election Process in OSPF

In OSPF (Open Shortest Path First), the Designated Router (DR) and Backup Designated Router (BDR) election is a critical mechanism that reduces the number of adjacencies required on multi-access networks, such as Ethernet broadcast segments. The election is based on two key parameters: the OSPF interface priority and the Router ID (RID). The router with the highest priority becomes the DR; if there is a tie, the router with the highest Router ID wins. The second-highest becomes the BDR. By default, the OSPF priority is 1 on Cisco routers, but it can be set to 0 to prevent a router from ever becoming a DR or BDR. The Router ID is typically the highest loopback interface IP address or, if none, the highest physical interface IP address that is active. 

The election process occurs only during the initial formation of neighbor relationships or when the current DR or BDR fails. It is not preemptive: once a DR and BDR are elected, they remain in their roles even if a router with a higher priority or Router ID joins the network later, unless a manual reset (like clearing the OSPF process) is performed. This non-preemptive behavior ensures stability and avoids constant re-elections that would disrupt routing. The election process uses OSPF Hello packets: routers include their priority and Router ID in the Hello messages, and they compare these values to determine the DR and BDR. The router that sees itself with the highest priority and Router ID will declare itself as the DR or BDR after the wait timer expires. 

Understanding this election process is essential for exam candidates because OSPF questions frequently test the criteria for DR and BDR selection, the non-preemptive nature, and the role of priority. For example, on the CCNA or Network+ exams, you might be asked to identify which router becomes the DR given a set of priorities and Router IDs, or how to influence an election by adjusting the priority interface parameter. Misunderstandings often arise around the fact that the DR is not elected based on routing capabilities but purely on static parameters, which means a less powerful router might become the DR if its priority is higher. This knowledge helps network engineers design stable OSPF networks and troubleshoot adjacency issues effectively.

## Designated Router Role on Multi-Access Networks

The Designated Router (DR) plays a central role in OSPF multi-access networks, such as Ethernet LANs, by acting as the focal point for link-state information exchange. On these networks, every OSPF router forms a full adjacency only with the DR and the Backup Designated Router (BDR), rather than with every other router on the segment. This drastically reduces the number of adjacencies from O(n^2) to O(n). For example, on a network with 10 routers, without a DR, 45 full adjacencies would be needed (n*(n-1)/2). With a DR and BDR, each router only forms two adjacencies (one to the DR and one to the BDR), resulting in a total of 18 adjacencies. This greatly reduces the overhead of LSU (Link-State Update) flooding and database synchronization. 

The DR is responsible for generating network link advertisements (Network LSA, Type 2) that describe all routers attached to the network segment. The DR also receives LSUs from all routers and forwards them to all neighbors using the multicast address 224.0.0.5 (AllSPFRouters). The DR ensures that every router on the segment has a consistent view of the link-state database. If the DR fails, the BDR takes over immediately, ensuring minimal disruption. The DR and BDR roles are only relevant on broadcast and NBMA (Non-Broadcast Multi-Access) network types. On point-to-point links, no DR/BDR election is performed because only two routers exist. 

Exam-focused content often tests the specific responsibilities of the DR, such as generating the Network LSA and establishing adjacencies with all other routers on the segment. For the AWS SAA exam, understanding DR concepts in OSPF can translate to understanding route propagation in virtual private clouds (VPCs) using dynamic routing. Similarly, for the Azure AZ-104 exam, concepts of DR may appear in context of virtual network gateway route tables. The DR role also impacts troubleshooting: if the DR is misconfigured or fails, network convergence delays can occur. A common exam scenario involves determining why OSPF adjacencies are stuck in the EXSTART state, which may be due to DR election problems. Therefore, mastering the DR role on multi-access networks is fundamental for any network or cloud certification.

## Designated Router Cost and Neighborship Impact

The Designated Router (DR) concept in OSPF directly influences the cost of routing on multi-access networks and the way neighborship is established. The cost of a route in OSPF is based on the reference bandwidth divided by the interface bandwidth; however, in the context of a DR, the cost is associated with the path through the DR to reach other routers on the same segment. All routers on a broadcast segment communicate via the DR, meaning that traffic from Router A to Router C on the same segment must go through the DR (and BDR for backup), even if they are directly connected at Layer 2. This can introduce a suboptimal path from a Layer 3 perspective, but it simplifies the link-state database and reduces overall flooding overhead. 

The cost to reach the DR is calculated based on the OSPF interface cost of the link between the router and the DR. Since the DR is typically a router with high bandwidth interfaces (or intentionally configured priority), the cost is usually low. However, if the DR is not positioned optimally (e.g., running on a slow link), traffic may traverse a higher-cost path, degrading performance. In exam questions, you may see scenarios where the DR election leads to higher-than-expected path costs, and candidates need to adjust OSPF priorities to move the DR to the most appropriate router. 

Neighborship between a DR and a non-DR router (called DRother) goes through specific states: Down, Init, 2-Way (only on broadcast networks), ExStart, Exchange, Loading, and Full. During the DR election, routers exchange Hello packets and transition to 2-Way state. The DR then forms full adjacency with all other routers. The BDR also forms full adjacency with all routers, but only the DR sends the Network LSA. On DRother routers, they only elect neighbors but do not form full adjacency with each other; they remain in 2-Way state. This is a key point tested in the CCNA and Network+ exams: a router may have many neighbors on a segment but only two fully adjacent relationships. Understanding this state machine helps troubleshoot OSPF issues like stuck adjacencies or network loops. 

For the Security+ and A+ exams, while they do not directly test OSPF, the concept of reducing complexity (adjacency reduction) mirrors security principles of minimizing attack surfaces. The AWS SAA and Google ACE exams might use similar logic when discussing route propagation in virtual networks. Ultimately, the practical impact of DR cost on routing decisions and the unique state mechanics of DR-based neighborships are essential for real-world OSPF deployment and exam success.

## Designated Router Deployment Best Practices

Deploying the Designated Router (DR) effectively requires careful planning to ensure OSPF network scalability, stability, and optimal performance. One best practice is to design the network so that the DR is a router with high processing power and adequate memory, since the DR handles the majority of LSU flooding and maintains adjacencies with all other routers on the segment. On critical segments, it is wise to configure an explicit OSPF priority of 255 on the intended DR router to guarantee its selection, and a priority of 1 on the intended BDR. Remaining routers should have default priority (1) or be set to 0 if they should never participate in the election. Setting a router's priority to 0 prevents it from becoming a DR or BDR but still allows it to form adjacencies with the elected DR/BDR. 

Another key best practice is to avoid using the highest Router ID as the sole criterion for election, as this can lead to unintended DR placement. Instead, manually configure priorities to reflect the network topology and redundancy requirements. For instance, in a data center, the core switch might be the DR, while a redundant aggregation switch serves as the BDR. This design ensures that inter-VLAN traffic traverses the optimal path without unnecessary hops. In cloud environments like AWS VPCs or Azure virtual networks, the DR concept does not directly exist, but the architectural principle of designating a central route distribution point (e.g., a transit gateway or virtual gateway) aligns with this best practice for route optimization. 

From a security perspective, OSPF authentication (MD5 or SHA) should be enabled on all interfaces, especially those participating in DR elections, to prevent rogue routers from injecting bogus LSUs or hijacking the DR role. Passive interfaces should be configured where needed to minimize unnecessary adjacencies. In large networks, implementing OSPF areas (e.g., stub areas, NSSA) can reduce the DR's load by limiting the scope of LSAs it must process. The DR should ideally reside in the backbone area (Area 0) for consistency. 

Exam preparation for certifications like CCNA, Network+, and AZ-104 must include these deployment considerations. Questions often ask about the implications of priority 0, how to influence the election, or why OSPF authentication is important. Troubleshooting scenarios may involve a misconfigured DR causing routing blackholes, where the BDR does not take over due to incorrect priority settings. By following these best practices, network engineers can ensure reliable OSPF operations and avoid common pitfalls that appear in practical exams and real-world implementations.

## Common mistakes

- **Mistake:** Thinking that all OSPF neighbors must be in FULL state.
  - Why it is wrong: On multi-access networks, DROTHER routers only form full adjacency with the DR and BDR, not with each other. Being in 2WAY state is normal and does not indicate an error.
  - Fix: Understand that the DR/BDR mechanism reduces adjacencies. Check the neighbor state along with the role (DR/BDR/DROTHER) to determine if the state is appropriate.
- **Mistake:** Assuming that a router with the highest priority always becomes DR immediately after configuration.
  - Why it is wrong: OSPF DR election is non-preemptive. Once a DR is elected, it remains DR until it fails, even if a router with a higher priority joins later. The higher priority router will only become DR if the current DR goes down.
  - Fix: To force a new election, you must reset the OSPF process or reload the routers. In a lab, you can use 'clear ip ospf process' to trigger a new election.
- **Mistake:** Confusing the DR role with the BDR role in the context of LSA flooding.
  - Why it is wrong: The DR is the primary point for LSA flooding. The BDR listens but does not flood LSAs. Some learners think both DR and BDR flood, but only the DR performs the actual flooding to all routers.
  - Fix: Remember that the BDR is a standby. It receives all LSAs but does not generate or forward them unless it becomes the DR after a failure.
- **Mistake:** Setting OSPF priority to 0 thinking it will prevent the router from participating in OSPF entirely.
  - Why it is wrong: Priority 0 only prevents a router from becoming DR or BDR. The router still participates in OSPF as a DROTHER and forms adjacencies with the DR and BDR.
  - Fix: If you want a router to not participate in OSPF at all, you should remove the OSPF configuration from that interface or use a network statement that does not include it.
- **Mistake:** Believing that DR election happens on point-to-point links.
  - Why it is wrong: OSPF DR election only occurs on broadcast and NBMA multi-access networks. Point-to-point and point-to-multipoint networks do not elect a DR or BDR because only two routers form an adjacency.
  - Fix: Check the OSPF network type on the interface. Use 'ip ospf network point-to-point' if connecting only two routers to avoid unnecessary DR election.

## Exam trap

{"trap":"A question gives a scenario where a new router with a higher priority is added to the network, and the candidate assumes it will immediately become the new DR.","why_learners_choose_it":"Learners often assume that OSPF election is like a vote where the highest priority always wins immediately. They do not remember the non-preemptive nature of the election.","how_to_avoid_it":"Remember that DR election occurs only at the initial OSPF startup or when the existing DR fails. A new router with higher priority will not preempt the current DR. If you see such a question, the correct answer is that the existing DR remains until it goes down or the OSPF process is reset."}

## Commonly confused with

- **Designated Router vs Backup Designated Router (BDR):** The BDR is the standby router that takes over if the Designated Router fails. Both are elected together, but the BDR does not flood LSAs. Many learners think the BDR and DR have the same role, but the BDR only listens until it becomes DR. (Example: In a team, the DR is the manager who sends the memo. The BDR is the assistant who reads the memo but does not send it unless the manager is absent.)
- **Designated Router vs DROTHER:** DROTHER refers to any router on the multi-access network that is not the DR or BDR. These routers form full adjacencies only with the DR and BDR. They remain in 2-way state with each other. Confusing DROTHER with DR is a common mistake. (Example: In a class, the DR is the teacher, the BDR is the assistant teacher, and all other students are DROTHERs. Students talk to the teacher and assistant, but not directly to each other for official announcements.)
- **Designated Router vs Designated Intermediate System (DIS) in IS-IS:** IS-IS, another link-state routing protocol, uses a similar concept called Designated Intermediate System (DIS) on broadcast networks. However, unlike OSPF, IS-IS election is preemptive, and the DIS can be replaced if a higher-priority router comes online. Also, IS-IS does not have a Backup DIS. (Example: Think of OSPF DR like an elected club president who stays until resignation. IS-IS DIS is like a president who can be voted out immediately if a more popular candidate appears.)
- **Designated Router vs Route Reflector in BGP:** BGP uses Route Reflectors to reduce the number of iBGP peering sessions, similar to how OSPF DR reduces adjacencies. However, Route Reflectors are a server-client model where clients send updates to the reflector, which then forwards them to other clients. OSPF DR is not a server; it uses multicast and all routers are peers. Also, BGP does not have an election for Route Reflector. (Example: BGP Route Reflector is like a central mailroom that forwards letters. OSPF DR is like a town crier who shouts news to everyone.)

## Step-by-step breakdown

1. **1. Multi-access network detection** — When OSPF is enabled on an interface, the router checks the network type. For Ethernet and other broadcast networks, the interface defaults to the broadcast network type, which triggers the DR election process. For NBMA networks like Frame Relay, the election still occurs but requires manual neighbor configuration.
2. **2. Hello packet exchange** — Routers start sending OSPF Hello packets every 10 seconds (by default on broadcast networks) to the multicast address 224.0.0.5. These Hello packets contain the router's priority, Router ID, and the list of neighbors it has seen. This is how routers discover each other and begin the election.
3. **3. DR and BDR election initiation** — Each router examines the Hello packets it receives. It looks at the priority and Router ID fields of all routers on the segment. The election algorithm selects the router with the highest priority to be the DR. If there is a tie, the router with the highest Router ID wins. Similarly, the second highest becomes the BDR.
4. **4. Non-preemptive role assignment** — Once the DR and BDR are elected, they keep their roles indefinitely. Even if a router with a higher priority joins later, it will not take over. This ensures stability and avoids constant role changes that could disrupt network convergence.
5. **5. Adjacency formation with DR and BDR** — All routers on the segment form full OSPF adjacencies (state: FULL) with both the DR and BDR. They exchange LSAs, database description packets, and synchronize their link-state databases. Routers that are not DR or BDR do not form full adjacencies with each other; they remain in 2-way state.
6. **6. LSA flooding via multicast** — When a non-DR router has a new LSA to advertise, it sends the LSA to the DR and BDR using the multicast address 224.0.0.6 (AllDRouters). The DR then flushes this LSA to all other routers on the segment using multicast 224.0.0.5 (AllSPFRouters). The BDR listens but does not forward LSAs.
7. **7. BDR takeover on DR failure** — If the DR fails (stops sending Hello packets), the BDR detects the absence after a dead interval (usually 40 seconds on broadcast networks). The BDR then assumes the role of DR and immediately begins flooding LSAs. A new BDR election is held among the remaining routers. This ensures minimal disruption.
8. **8. DR re-election after OSPF reset** — If an administrator resets the OSPF process (e.g., 'clear ip ospf process'), a new DR election occurs. All routers start from scratch, and the highest priority router at that moment becomes the new DR. This can be used purposefully to force a desired DR after configuration changes.

## Practical mini-lesson

In real-world networks, the Designated Router concept is not just theoretical; it has direct operational implications. When you configure OSPF on a Cisco or Juniper router, you need to be aware of which interfaces are on multi-access segments. For example, if you connect two routers via a direct fiber link, that is a point-to-point link. You can change the OSPF network type to 'point-to-point' to avoid unnecessary DR election, which saves a few seconds in convergence time and simplifies troubleshooting.

When designing a network, consider which router should become the DR. Typically, you want a router with high CPU and memory resources to be the DR because it will handle the LSA flooding for the entire segment. You can set the OSPF priority on the interface to ensure your designated core router wins the election. For example, on a Cisco router, use 'interface GigabitEthernet0/0', then 'ip ospf priority 200'. On the router you want to be BDR, set priority to 100. On all other routers, set priority to 0 or leave default (1). Setting priority to 0 ensures they never become DR or BDR, reducing overhead.

What can go wrong? A common issue is that after adding a new router with higher priority, the network does not see it become DR. This confuses administrators who expect immediate change. You must remember that OSPF is non-preemptive. To force a new election, you can use the 'clear ip ospf process' command on all routers, but this is disruptive because it tears down all adjacencies. A less invasive approach is to reload the DR, which will trigger a new election and allow the new router to become DR.

Another potential problem is incorrect neighbor states. If you see a router stuck in EXSTART/EXCHANGE state, it may indicate a mismatched MTU or authentication issue, not necessarily DR. But if you see a router in 2WAY state with another DROTHER, that is normal. Use 'show ip ospf neighbor' to verify roles. The output shows 'DR', 'BDR', or 'DROTHER' next to each neighbor.

Professionals also need to consider that in NBMA environments, you must manually specify neighbors if the network does not support broadcast. In such cases, all routers need to be configured with 'neighbor' statements on the hub router. This is more complex and error-prone. Understanding these nuances is essential for network engineers.

Finally, remember that in OSPFv3 (for IPv6), the DR election mechanism is the same, but the Router ID is still derived from an IPv4 address (if configured) or manually set. The same principles apply. Practice configuring OSPF on a simulator to see the DR election in action. It will solidify your understanding.

## Commands

```
interface GigabitEthernet0/1
 ip ospf priority 255
```
Sets the OSPF priority on an interface to 255, ensuring this router becomes the Designated Router (DR) on that network segment.

*Exam note: Testing the priority parameter to influence DR election is a classic CCNA and Network+ exam question. Know that 0 means never DR/BDR and higher values win.*

```
interface GigabitEthernet0/2
 ip ospf priority 1
```
Sets the OSPF priority to 1 (default) but can be used explicitly to ensure a router becomes the Backup Designated Router (BDR) if no higher priority router exists.Good for redundancy planning.

*Exam note: Exam questions often use priorities of 1 for BDR candidate. Remember: highest priority wins, then highest Router ID.*

```
router ospf 1
 router-id 10.0.0.1
```
Manually sets the Router ID to 10.0.0.1, which is used as a tie-breaker in DR elections when priorities are equal.

*Exam note: Router ID manipulation is a common technique tested in CCNA. Ensure the Router ID is unique and reachable. Loopback interfaces are often used instead.*

```
clear ip ospf process
```
Resets the OSPF process on the router, forcing new DR/BDR elections on all interfaces. Used to apply new priority or Router ID changes without reloading the router.

*Exam note: This command appears in exam scenarios triggering a new election. Be aware that it disrupts routing temporarily and is not needed if only non-DR routers join.*

```
interface GigabitEthernet0/3
 ip ospf network point-to-point
```
Changes the OSPF network type on an interface to point-to-point, which eliminates the need for DR/BDR election entirely, reducing adjacency overhead.

*Exam note: The network type is a critical concept. On point-to-point links, no DR is elected. This simplifies adjacencies and is often tested in CCNA and Network+ labs.*

```
debug ip ospf adj
```
Enables debugging of OSPF adjacency events, including detailed information about DR/BDR election state transitions (e.g., DR identification and neighbor state changes).

*Exam note: This debug command helps troubleshoot DR election issues, but is too intensive for production. Exam questions may ask about the output for understanding adjacency failures.*

```
router ospf 1
 passive-interface default
```
Configures all interfaces as passive for OSPF by default, then selectively enables OSPF on interfaces that need adjacencies, preventing unwanted DR elections on unwanted links.

*Exam note: Passive interfaces do not form adjacencies, thus no DR election. Common in security-focused exams like Security+ and AZ-104 to reduce attack surface.*

## Troubleshooting clues

- **Router fails to become DR despite higher priority** — symptom: A router with priority 255 is not elected as DR; instead, a lower priority router is DR.. DR election is non-preemptive. If the current DR was elected before the higher-priority router joined, it remains DR until the OSPF process is reset or it fails. The new router, despite higher priority, only becomes BDR (if eligible) or DRother. (Exam clue: Exam questions often present a scenario where a router with priority 255 joins after election and ask why it is not DR. The answer is non-preemptive property.)
- **All routers stuck in 2-Way state** — symptom: Routers on a broadcast segment show OSPF neighbor as 2-Way and do not transition to Full.. On multi-access networks, DRother routers only reach 2-Way with each other; they only form Full adjacency with the DR and BDR. If no router is elected DR or BDR, all neighbors will remain in 2-Way. This can happen if the DR election fails due to interface misconfigurations or if all routers have priority 0. (Exam clue: Questions may show a neighbor state of 2-Way and ask why. The answer is that DRother routers do not go to Full with each other.)
- **BDR not taking over after DR failure** — symptom: DR goes down but BDR does not become DR; routing convergence is delayed or fails.. The BDR only becomes DR if it physically detects the DR failure through lack of Hello packets (Dead interval). Possible reasons: BDR also fails simultaneously, network segmentation, or the BDR is not configured correctly (e.g., priority 0 on BDR). If the BDR was not in Full state with all routers, it will not immediately assume DR role. (Exam clue: Exam scenario: DR fails, but BDR does not take over. Correct answer often involves checking the dead timer or that BDR was not fully adjacent.)
- **Excessive LSU flooding from DR** — symptom: High CPU usage on the DR router; network bandwidth consumed by repeated LSUs.. The DR is responsible for flooding LSUs to all neighbors. If there are many routers on the segment or frequent route changes, the DR may be overwhelmed. This can be due to misconfigured timers (e.g., hello/dead intervals too short) or flapping interfaces causing constant LSA updates. (Exam clue: Troubleshooting CPU spikes on DR typically points to frequent routing updates or unstable interfaces. Exam may test the understanding that DR handles all LS flooding.)
- **OSPF neighbor stuck in EXSTART due to DR mismatch** — symptom: Two routers are stuck in the ExStart/Exchange state; the DR election never completes.. This occurs when both routers believe they should be the master during adjacency formation. On broadcast networks, the DR is the master for the exchange process. If there is a disagreement about who the DR is (e.g., both think each other is DR), the state machine stalls. This can happen if the network type is mismatched (e.g., one side broadcast, other non-broadcast). (Exam clue: Exam CCNA: Stuck in ExStart often due to MTU mismatch or OSPF network type mismatch. Check MTU and network type on both sides.)
- **DR election causes suboptimal routing path** — symptom: Traffic between two routers on same segment is routed through a slow link or higher-cost path via the DR.. By design, traffic between DRother routers must pass through the DR. If the DR is not the optimal router (e.g., low bandwidth interface), the path cost increases. This can be fixed by adjusting OSPF priority to make a better-placed router the DR. (Exam clue: Exam scenario: Two routers on same segment but traffic slow. Answer: Use ip ospf priority to move DR to the router with higher bandwidth link.)
- **DR not generating Network LSA (Type 2)** — symptom: OSPF database shows no Network LSA for the broadcast segment, causing routing blackholes.. Only the DR generates the Network LSA. If the DR fails or is incorrectly configured (e.g., interface OSPF network type is point-to-point), no Type 2 LSA is generated, and other routers cannot calculate routes to that segment. Also, if the DR is not adjacent to all neighbors, the LSA may be incomplete. (Exam clue: Exam will test that the DR must be fully adjacent to all neighbors to generate Type 2 LSA. Missing Type 2 LSA points to DR issues.)
- **OSPF adjacency stuck in Init state with DR** — symptom: A router sees the DR in the neighbor table but state remains Init.. This means the router has received Hello from DR but its own Hello is not being received by DR (uni-directional communication). Could be due to ACLs blocking multicast, mismatched subnet masks, or authentication key mismatch. (Exam clue: In exams, Init state indicates one-way communication. Check for ACLs, multicast group 224.0.0.5 filtering, or subnet mask mismatch.)

## Memory tip

Think 'DR = Decreases Traffic', the DR reduces the number of OSPF adjacencies and LSA flooding, making the network more efficient.

## FAQ

**Do I need to configure priority for OSPF to work?**

No, OSPF works with default priority values (1 on Cisco). The DR election will still occur based on the highest Router ID if all priorities are equal. You only need to configure priority if you want to control which router becomes DR or BDR.

**What happens if the BDR fails but the DR is still up?**

The DR continues to operate normally. A new BDR election is triggered, and the router with the highest priority among the remaining becomes the new BDR. There is no network disruption because the DR is still flooding LSAs.

**Can a router be a DR on one interface and a DROTHER on another?**

Yes, DR election is per interface (per network segment). A router can be the DR on one VLAN but a DROTHER on another, depending on the priorities and Router IDs of routers on each segment.

**Why do my OSPF neighbors show as 2WAY instead of FULL?**

On a multi-access network, DROTHER routers only form full adjacencies with the DR and BDR. If two DROTHER routers see each other, they will remain in 2WAY state. This is normal and not a problem.

**How can I force a new DR election without reloading all routers?**

You can use the 'clear ip ospf process' command on the current DR, or reload the DR router. This will cause the DR to go down, prompting the BDR to take over and a new election to occur among the remaining routers.

**Does the DR concept apply to OSPFv3?**

Yes, OSPFv3 for IPv6 uses the same DR/BDR election mechanism on broadcast and NBMA networks. The Router ID is still an IPv4 address (if configured) or manually assigned.

**What is the difference between DR and a Route Reflector in BGP?**

DR is elected automatically in OSPF and reduces the number of adjacencies. Route Reflector in BGP is a manually configured server that reduces iBGP mesh. DR uses multicast for flooding; Route Reflector uses TCP sessions. Both solve similar scalability problems but in different protocols.

## Summary

The Designated Router is a cornerstone concept in OSPF, a link-state routing protocol widely used in enterprise and data center networks. Its primary role is to reduce the number of OSPF adjacencies and control the flooding of Link State Advertisements on multi-access networks like Ethernet. By electing a single router to manage LSA distribution, OSPF avoids the n-squared adjacency problem and ensures efficient use of bandwidth and CPU resources. The Backup Designated Router provides redundancy, taking over if the DR fails. Understanding the election process, which is based on priority and Router ID and is non-preemptive, is critical for both network configuration and troubleshooting.

In certification exams, particularly CCNA and Network+, the DR topic appears in configuration, scenario, and troubleshooting questions. You must be able to interpret 'show ip ospf neighbor' output, understand the default behavior, and know how to influence election results. For cloud certifications, DR knowledge supports broader network understanding.

Key takeaways: DR election occurs only on broadcast and NBMA networks. DROTHER routers remain in 2-way state with each other. The election is non-preemptive. The DR uses multicast 224.0.0.6 to receive updates and 224.0.0.5 to flood them. Mastering these concepts will help you pass your exams and be a better network professional.

---

Practice questions and the full interactive page: https://courseiva.com/glossary/designated-router