diff --git a/src/pages/how-to/accessing-entire-domains-within-networks.mdx b/src/pages/how-to/accessing-entire-domains-within-networks.mdx index 39377cec..74c4a196 100644 --- a/src/pages/how-to/accessing-entire-domains-within-networks.mdx +++ b/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. + + DNS Forwarder port change: starting with NetBird v0.59.0, the local DNS forwarder used for routed DNS routes switches from port 5353 to 22054 to avoid collisions on client devices. For backward compatibility, the Management Service applies the new port only when all peers in the account run v0.59.0 or newer. If any peer is below v0.59.0, port 5353 will be used for all peers in that account. + + ## Setting Up Developers' Network Environment To create a network for the developer environment: diff --git a/src/pages/how-to/manage-dns-in-your-network.mdx b/src/pages/how-to/manage-dns-in-your-network.mdx index 656385eb..6d0ea7c1 100644 --- a/src/pages/how-to/manage-dns-in-your-network.mdx +++ b/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. + + DNS Forwarder port change: starting with NetBird v0.59.0, the local DNS forwarder used for routed DNS routes switches from port 5353 to 22054 to avoid collisions on client devices. For backward compatibility, the Management Service applies the new port only when all peers in the account run v0.59.0 or newer. If any peer is below v0.59.0, port 5353 will be used for all peers in that account. + + ### 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. diff --git a/src/pages/how-to/networks.mdx b/src/pages/how-to/networks.mdx index 230353de..138d1c12 100644 --- a/src/pages/how-to/networks.mdx +++ b/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. + + DNS Forwarder port change: starting with NetBird v0.59.0, the local DNS forwarder used for routed DNS routes switches from port 5353 to 22054 to avoid collisions on client devices. For backward compatibility, the Management Service applies the new port only when all peers in the account run v0.59.0 or newer. If any peer is below v0.59.0, port 5353 will be used for all peers in that account. + + ## Differences between Networks and Network Routes | | Networks | Network routes | diff --git a/src/pages/how-to/routing-traffic-to-private-networks.mdx b/src/pages/how-to/routing-traffic-to-private-networks.mdx index ae677bcb..2de0368c 100644 --- a/src/pages/how-to/routing-traffic-to-private-networks.mdx +++ b/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. + + DNS Forwarder port change: starting with NetBird v0.59.0, the local DNS forwarder used for routed DNS routes switches from port 5353 to 22054 to avoid collisions on client devices. For backward compatibility, the Management Service applies the new port only when all peers in the account run v0.59.0 or newer. If any peer is below v0.59.0, port 5353 will be used for all peers in that account. + + ### 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.