OSPF DR and BDR Election: How It Works and How to Control It

On multi-access OSPF networks, the DR and BDR centralize LSA exchange so routers do not flood 45 sessions across 10 neighbors. A practical guide to what the DR and BDR do and why OSPF design depends on them.

OSPF DR and BDR: What They Are and Why They Matter - PingLabz OSPF article title card

The Solution: DR and BDR

OSPF solves this with two special routers:

If you want the bigger picture first, the OSPF complete guide covers the architecture this article plugs into.

Designated Router (DR)

What it is:
The central point for LSA exchange on a multi-access network.

What it does:

  • Forms full adjacencies with all other routers
  • Generates the Type 2 Network LSA for the segment
  • Receives LSA updates from all routers and redistributes them

Multicast address: 224.0.0.6 (AllDRouters)

Backup Designated Router (BDR)

What it is:
The backup to the DR.

What it does:

  • Forms full adjacencies with all other routers (just like the DR)
  • Listens to all LSA traffic
  • Takes over if the DR fails (no election needed - it's already synchronized)

Why it exists:
Provides instant failover without needing to re-elect and re-synchronize.

DROther

What it is:
All routers that are not the DR or BDR.

What they do:

  • Form full adjacencies with the DR and BDR
  • Form 2-Way adjacencies with each other (no LSA exchange)
  • Send LSA updates to the DR (224.0.0.6)

How DR/BDR Reduces Overhead

Without DR/BDR (5 routers):

  • Full adjacencies: 10
  • LSA flooding: Every router floods to every other router

With DR/BDR (5 routers):

  • Full adjacencies: 7 (the DR and the BDR each go FULL with the other 4 routers; the DR-BDR adjacency counts once)
  • LSA flooding: DROthers send to DR, DR redistributes
  • Result: 30% fewer adjacencies, far less flooding

DR/BDR Election Process

When Election Happens

  • When the first two routers come online on a segment
  • When the DR fails and there's no BDR
  • NOT when a router with higher priority joins (election is non-preemptive)

Election Rules

Step 1: Check OSPF Priority
The router with the highest OSPF priority becomes the DR.
The router with the second-highest priority becomes the BDR.

Default priority: 1
Range: 0-255
Priority 0: Router will never become DR or BDR (use this for weak routers)

Step 2: Tiebreaker (Router ID)
If priorities are equal, the router with the highest Router ID wins.

Example Election

Scenario:
4 routers on the same Ethernet segment:

100
RouterR1
Router ID1.1.1.1
ResultDR (highest priority)
50
RouterR2
Router ID2.2.2.2
Result
BDR (second-highest priority)
1
RouterR3
Router ID3.3.3.3
ResultDROther
1
RouterR4
Router ID4.4.4.4
ResultDROther

Even though R4 has the highest Router ID (4.4.4.4), R1 becomes DR because of priority.

I built this exact segment in my home lab: four IOL routers (IOS XE 17.18.2), each with Ethernet0/1 on 192.168.1.0/24, joined through an IOL-L2 switch in VLAN 10. Router IDs are 1.1.1.1 to 4.4.4.4 and the priorities are the ones in the table. Every output in this article comes from that lab, using Ethernet0/1 rather than a GigabitEthernet port.

Topology diagram: four IOL routers R1 to R4 on one broadcast segment, each using Ethernet0/1 on 192.168.1.1 to .4/24 through SW1 in access VLAN 10. R1 is the DR with priority 100, R2 is the BDR with priority 50, and R3 and R4 are DROTHERs with priority 1. R3's neighbor table shows FULL with the DR and BDR and 2WAY with R4.

Election is Non-Preemptive

Key point:
Once a DR is elected, it stays the DR until it goes down - even if a router with higher priority joins later.

Example:

  1. In the lab, R2, R3 and R4 came up first while R1's interface was shut. R2 (priority 50) became DR, and R4 won the BDR seat over R3 on Router ID.
  2. R1 (priority 100) was then enabled and joined the segment.
  3. R2 stayed DR and R4 stayed BDR. R1 came up as a DROTHER, even with the highest priority.
R1#show ip ospf interface Ethernet0/1
Ethernet0/1 is up, line protocol is up 
  Internet Address 192.168.1.1/24, Interface ID 3, Area 0
...
  Transmit Delay is 1 sec, State DROTHER, Priority 100
  Designated Router (ID) 2.2.2.2, Interface address 192.168.1.2
  Backup Designated router (ID) 4.4.4.4, Interface address 192.168.1.4
...
  Neighbor Count is 3, Adjacent neighbor count is 2 
    Adjacent with neighbor 2.2.2.2  (Designated Router)
    Adjacent with neighbor 4.4.4.4  (Backup Designated Router)
R1#show ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
2.2.2.2          50   FULL/DR         00:00:35    192.168.1.2     Ethernet0/1
3.3.3.3           1   2WAY/DROTHER    00:00:39    192.168.1.3     Ethernet0/1
4.4.4.4           1   FULL/BDR        00:00:33    192.168.1.4     Ethernet0/1

To force a new election:
Clear the OSPF process on the current DR:

Router# clear ip ospf process

⚠️ Warning: This disrupts OSPF on that router.

One clear is not always enough. When I cleared R2, the BDR (R4) was promoted to DR, and R1 only took the empty BDR seat:

R1#show ip ospf interface brief
Interface    PID   Area            IP Address/Mask    Cost  State Nbrs F/C
Lo0          1     0               1.1.1.1/32         1     LOOP  0/0
Et0/1        1     0               192.168.1.1/24     10    BDR   3/3
R1#show ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
2.2.2.2          50   FULL/DROTHER    00:00:35    192.168.1.2     Ethernet0/1
3.3.3.3           1   FULL/DROTHER    00:00:34    192.168.1.3     Ethernet0/1
4.4.4.4           1   FULL/DR         00:00:37    192.168.1.4     Ethernet0/1

A second clear ip ospf process on the new DR (R4) finished the job: R4 dropped out, R1 moved up from BDR to DR, and R2 was elected the new BDR. So it took two clears, on R2 and then on R4, to put the priority-100 router in charge.

Lab diagram: OSPF DR/BDR roles at each step of the election test. With R1 shut, R2 is DR and R4 is BDR. R1 joins with priority 100 but stays DROTHER because the election is non-preemptive. Clearing OSPF on R2 promotes R4 to DR and R1 to BDR. Clearing OSPF on R4 makes R1 the DR and R2 the BDR. With priority 0, R4 stays a DROTHER but is still FULL with the DR and BDR.

Controlling the DR/BDR Election

Set OSPF Priority

Default: 1
To make a router the DR: Set priority higher than other routers
To prevent a router from becoming DR/BDR: Set priority to 0

Configuration:

R1(config)# interface Ethernet0/1
R1(config-if)# ip ospf priority 100

Verification:

R1#show ip ospf interface Ethernet0/1
Ethernet0/1 is up, line protocol is up 
  Internet Address 192.168.1.1/24, Interface ID 3, Area 0
  Attached via Interface Enable
  Process ID 1, Router ID 1.1.1.1, Network Type BROADCAST, Cost: 10
...
  Transmit Delay is 1 sec, State DR, Priority 100
  Designated Router (ID) 1.1.1.1, Interface address 192.168.1.1
  Backup Designated router (ID) 2.2.2.2, Interface address 192.168.1.2
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
...
  Neighbor Count is 3, Adjacent neighbor count is 3 
    Adjacent with neighbor 2.2.2.2  (Backup Designated Router)
    Adjacent with neighbor 3.3.3.3
    Adjacent with neighbor 4.4.4.4

Key fields:

  • State: DR (this router is the DR)
  • Priority: 100
  • Designated Router: Shows the DR's Router ID and IP
  • Backup Designated Router: Shows the BDR's Router ID and IP

Example: Ensuring Core Router is DR

Scenario:
You have a core router (R1) and three access-layer routers (R2, R3, R4) on the same VLAN.

Goal:
Make R1 the DR so it handles LSA distribution (it has more CPU/bandwidth).

Configuration (R1):

Router(config)# interface vlan 10
Router(config-if)# ip ospf priority 200

Configuration (R2, R3, R4):

Router(config)# interface vlan 10
Router(config-if)# ip ospf priority 50

Result:
R1 becomes DR (priority 200).
The router with priority 50 and highest Router ID becomes BDR.

Example: Preventing a Router from Becoming DR

Scenario:
R5 is a low-end router. You don't want it handling DR responsibilities.

Configuration (R5):

Router(config)# interface gi0/0
Router(config-if)# ip ospf priority 0

Result:
R5 will never become DR or BDR on this segment.

In the lab I set R4 to priority 0 and cleared its OSPF process. It came back as a DROTHER with priority 0, and it still went FULL with the DR and BDR, so priority 0 removes a router from the election, not from OSPF:

R4#show ip ospf interface Ethernet0/1
...
  Transmit Delay is 1 sec, State DROTHER, Priority 0
  Designated Router (ID) 1.1.1.1, Interface address 192.168.1.1
  Backup Designated router (ID) 2.2.2.2, Interface address 192.168.1.2
...
  Neighbor Count is 3, Adjacent neighbor count is 2 
    Adjacent with neighbor 1.1.1.1  (Designated Router)
    Adjacent with neighbor 2.2.2.2  (Backup Designated Router)

DR/BDR on Different Network Types

Broadcast (Ethernet, default)

  • DR/BDR: Yes
  • Full adjacencies: DR ↔ all, BDR ↔ all
  • DROther adjacencies: 2-Way with each other

Point-to-Point

  • DR/BDR: No (not needed - only 2 routers)
  • Full adjacencies: Both routers always Full

NBMA (Frame Relay, ATM)

  • DR/BDR: Yes
  • Complication: NBMA doesn't support multicast, so you need manual neighbor statements

Point-to-Multipoint

  • DR/BDR: No
  • Full adjacencies: All routers form full adjacencies

Learn more: OSPF Network Types Explained

Verifying DR/BDR Status

Check Interface State

R1#show ip ospf interface brief
Interface    PID   Area            IP Address/Mask    Cost  State Nbrs F/C
Lo0          1     0               1.1.1.1/32         1     LOOP  0/0
Et0/1        1     0               192.168.1.1/24     10    DR    3/3

R3#show ip ospf interface brief
Interface    PID   Area            IP Address/Mask    Cost  State Nbrs F/C
Lo0          1     0               3.3.3.3/32         1     LOOP  0/0
Et0/1        1     0               192.168.1.3/24     10    DROTH 2/3

Key fields:

  • State: DR, BDR or DROTH (DROTHER) for this router on that segment
  • Nbrs F/C: FULL adjacencies / total neighbors. The DR shows 3/3; a DROTHER shows 2/3 because it stops at 2-Way with the other DROTHER
  • Detail: use show ip ospf interface Ethernet0/1 for the priority and the DR/BDR Router IDs and addresses

Check Neighbors and Their Roles

R1#show ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
2.2.2.2          50   FULL/BDR        00:00:36    192.168.1.2     Ethernet0/1
3.3.3.3           1   FULL/DROTHER    00:00:37    192.168.1.3     Ethernet0/1
4.4.4.4           1   FULL/DROTHER    00:00:39    192.168.1.4     Ethernet0/1

What you see:

  • 2.2.2.2: the BDR, FULL
  • 3.3.3.3 and 4.4.4.4: DROTHERs, both FULL. R1 is the DR, so it goes FULL with every router on the segment

Now run the same command on R3, one of the DROTHERs:

R3#show ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
1.1.1.1         100   FULL/DR         00:00:35    192.168.1.1     Ethernet0/1
2.2.2.2          50   FULL/BDR        00:00:39    192.168.1.2     Ethernet0/1
4.4.4.4           1   2WAY/DROTHER    00:00:32    192.168.1.4     Ethernet0/1

Interpretation: the role after the slash is the neighbor's role, not yours. If every neighbor is FULL, you are the DR or the BDR. If one is 2WAY/DROTHER, you are a DROTHER yourself, and that 2-Way state with the other DROTHER is normal, not a fault.

Get the OSPF Field Reference - 9 pages, free

Everything you'd want to remember about OSPF on nine printable pages. State machine diagram, LSA types, troubleshooting decision tree, copy-paste IOS XE templates, and real lab captures. Free for PingLabz members - just sign up with your email.

Get the OSPF cheat-sheet

Common DR/BDR Issues

Problem 1: Wrong Router is DR

Symptom:
A low-power access switch became DR instead of the core router.

Cause:

  • The access switch booted first and won the election
  • Non-preemptive election means it stayed DR

Solution 1 (Temporary):
Clear OSPF process on the current DR:

Router# clear ip ospf process

The BDR is promoted to DR, and the election only fills the empty BDR seat. In the lab it took two clears, first on R2 and then on R4, before R1 (the highest priority) became DR.

Solution 2 (Permanent):
Set OSPF priorities correctly before deployment:

! Core router (should be DR)
Router(config-if)# ip ospf priority 200

! Access switches (should be DROther)
Router(config-if)# ip ospf priority 10

Problem 2: No BDR Elected

Symptom:
Only one router on the segment, so there's a DR but no BDR.

Cause:
BDR election requires at least 2 routers.

Impact:
If the DR fails, a new election must happen (slower failover).

Solution:
Ensure at least 2 routers are on multi-access segments in production.

Problem 3: DR/BDR Flapping

Symptom:
DR keeps changing.

Cause:

  • Current DR keeps rebooting
  • OSPF priority misconfigured (multiple routers fighting for DR)
  • Network instability

Solution:

  • Check DR router health (CPU, memory, crashes)
  • Verify OSPF priority consistency
  • Check for duplicate Router IDs

DR/BDR Best Practices

1. Set Priorities Explicitly in Production

Don't rely on default priority (1) and Router ID tiebreakers. Explicitly configure:

  • Core/distribution routers: Priority 100-200
  • Access routers: Priority 10-50
  • Weak devices: Priority 0

2. Make the Fastest Router the DR

The DR handles LSA redistribution. Make it the router with:

  • Most CPU
  • Most bandwidth
  • Best reliability

3. Use Priority 0 on User-Facing Routers

If a router only needs OSPF for reachability (not routing), set priority 0:

Router(config-if)# ip ospf priority 0

4. Document Your DR/BDR Design

In the network documentation, note:

  • Which routers should be DR/BDR
  • OSPF priorities per segment

5. Avoid Changing Priorities in Production

Changing OSPF priority won't trigger an immediate re-election. You'd need to clear the OSPF process, which disrupts routing.

Best practice:
Set priorities correctly during initial deployment.

DR/BDR in Multi-Area Environments

Key point:
DR/BDR election is per-segment, not per-area.

Example:
A router can be:

  • DR on VLAN 10 (Area 0)
  • DROther on VLAN 20 (Area 10)

Each segment elects its own DR/BDR independently.

Summary: DR/BDR Checklist

Now you know:

✅ Why DR/BDR exist - Reduce adjacencies and LSA flooding on multi-access networks
✅ How election works - Highest priority, then highest Router ID
✅ Election is non-preemptive - DR stays DR until it fails
✅ How to control election - Set OSPF priority per interface
✅ When DR/BDR are used - Broadcast and NBMA networks only
✅ Common issues - Wrong router elected, DR flapping

Next Step:
DR/BDR is one piece of OSPF efficiency. The other is OSPF cost - the metric that determines the best path. Read How OSPF Calculates Metric and Cost next.

Internal Links:

💡
DR/BDR makes more sense after you elect one yourself. Use a browser OSPF lab, then the matching chapter in the CCNA lab book. Browse labs · free Essentials. Quiz yourself too: the free CCNA practice sample opens on IP routing questions with no account needed, and Pro adds 500 questions, two timed mock exams and 200 flashcards.

Read next