diff --git a/docs/routing/bird/bird.md b/docs/routing/bird/bird.md
index c1816ed..c20fd32 100644
--- a/docs/routing/bird/bird.md
+++ b/docs/routing/bird/bird.md
@@ -107,6 +107,8 @@ protocol kernel {
 }
 
 protocol babel crxn_net {
+    randomize router id on;
+
     interface "crxn_peer1" {
         type wired;
         rxcost 30;
@@ -226,6 +228,8 @@ The keyword `persist` can be used to prevent bird from deleting routes from the
 
 ```
 protocol babel crxn_net {
+    randomize router id on;
+
     interface "crxn_peer1" {
         type wired;
         rxcost 30;
@@ -246,6 +250,7 @@ With `interface "crxn*";` you can mark any interface starting with `crxn` as a p
 Therefore it makes sense to define a separate interface for each peer. As `type` there are `wired` and `wireless`. In general `wired` is always used. According to the `type` parameter babel is adjusted. With `rxcost` we define the "cost", which a peer needs to us. Without specification this is 96. Here it is recommended to take the latency as cost. If you want to avoid that packets are routed through you, you can increase the cost.
 In this example, there is a connection to our peer via the interface `crxn_peer1`. This is a wired connection with a latency of 30ms.
 
+`randomize router id on;` If a Babel peer is restarted in a short time, other peers may reject its routes. To prevent this, you can randomize the first 32 bits of your router ID at each startup, which will cause other Babel peers to think you are a "new" peer and therefore accept your routes.
 
 ```
 protocol device {}