From 4615be2c3e14019b6105d5312cc6df1c9527b4ef Mon Sep 17 00:00:00 2001
From: Bruno Mercier Costa <94469565+emrcbrn@users.noreply.github.com>
Date: Thu, 11 Jun 2026 16:37:15 +0200
Subject: [PATCH] Update ports-and-firewalls.mdx

adding relay.netbird.io as required
---
 src/pages/about-netbird/ports-and-firewalls.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/pages/about-netbird/ports-and-firewalls.mdx b/src/pages/about-netbird/ports-and-firewalls.mdx
index 832e64d82..88314c84d 100644
--- a/src/pages/about-netbird/ports-and-firewalls.mdx
+++ b/src/pages/about-netbird/ports-and-firewalls.mdx
@@ -57,7 +57,7 @@ NetBird usually won't need open ports, but sometimes you or your IT team needs t
     * In more restricted environments, `netbird status` will show `keepalive ping failed` errors without a firewall rule for TURN
         * Example `nftables` outbound firewall rule: `ip daddr turn.netbird.io tcp dport 443-65535 accept`
 * Relay service:
-  * **Endpoint**: *.relay.netbird.io
+  * **Endpoints**: *.relay.netbird.io and relay.netbird.io
   * **Port**: TCP/443
   * **IPv4**: The list is dynamic and geo-distributed; When looking at the `netbird status -d` output, you can see which relay you are connecting to.
   * It is advised to wildcard `*.relay.netbird.io` when possible, to avoid interrupts.