Add note about DNS forwarder port change

src/pages/how-to/accessing-entire-domains-within-networks.mdx

@@ -54,6 +54,10 @@ To enable DNS wildcard routing in your NetBird account, follow these steps:
     Once the feature is enabled, you may need to restart your routing peers and clients to apply the changes.
 </Note>
 
+<Note>
+    DNS Forwarder port change: starting with NetBird v0.59.0, the local DNS forwarder used for routed DNS routes switches from port <code>5353</code> to <code>22054</code> to avoid collisions on client devices. For backward compatibility, the Management Service applies the new port only when <strong>all peers in the account</strong> run v0.59.0 or newer. If any peer is below v0.59.0, port <code>5353</code> will be used for all peers in that account.
+</Note>
+
 ## Setting Up Developers' Network Environment
 
 To create a network for the developer environment:

src/pages/how-to/manage-dns-in-your-network.mdx

@@ -30,6 +30,10 @@ control what nameservers a specific [peer group](/how-to/manage-network-access#g
 To minimize system changes, NetBird runs a local embedded DNS resolver on each peer.
 This resolver handles queries for domain names of registered peers in your network and forwards queries to upstream nameservers that you configure in the system.
 
+<Note>
+    DNS Forwarder port change: starting with NetBird v0.59.0, the local DNS forwarder used for routed DNS routes switches from port <code>5353</code> to <code>22054</code> to avoid collisions on client devices. For backward compatibility, the Management Service applies the new port only when <strong>all peers in the account</strong> run v0.59.0 or newer. If any peer is below v0.59.0, port <code>5353</code> will be used for all peers in that account.
+</Note>
+
 ### Nameserver
 A nameserver is an upstream DNS server responsible for name resolution. If a query is not related to a peer domain name,
 it will be resolved by one of the upstream servers. You can assign private and public IPs, as well as custom ports for your nameservers.

src/pages/how-to/networks.mdx

@@ -89,6 +89,10 @@ You can enable DNS resolution on the routing peer by accessing your account `Set
     Once the feature is enabled, you may need to restart your routing peers and clients to apply the changes.
 </Note>
 
+<Note>
+    DNS Forwarder port change: starting with NetBird v0.59.0, the local DNS forwarder used for routed DNS routes switches from port <code>5353</code> to <code>22054</code> to avoid collisions on client devices. For backward compatibility, the Management Service applies the new port only when <strong>all peers in the account</strong> run v0.59.0 or newer. If any peer is below v0.59.0, port <code>5353</code> will be used for all peers in that account.
+</Note>
+
 ## Differences between Networks and Network Routes
 
 |                                                                           | Networks                                                                                                          | Network routes                                                                                                                      |

src/pages/how-to/routing-traffic-to-private-networks.mdx

@@ -78,6 +78,10 @@ The purpose of the keep routes functionality is to retain previously resolved ro
     Currently, wildcard domains are not supported for DNS routes.
 </Note>
 
+<Note>
+    DNS Forwarder port change: starting with NetBird v0.59.0, the local DNS forwarder used for routed DNS routes switches from port <code>5353</code> to <code>22054</code> to avoid collisions on client devices. For backward compatibility, the Management Service applies the new port only when <strong>all peers in the account</strong> run v0.59.0 or newer. If any peer is below v0.59.0, port <code>5353</code> will be used for all peers in that account.
+</Note>
+
 ### Metric and priority
 Metric defines prioritization when choosing the main routing peer in a high availability network. Lower metrics have higher priority.
 Outside of high availability routes, the metric has no effect.