From 9545fa09e25a87823e5dc5787ad63f8740e17c5b Mon Sep 17 00:00:00 2001
From: Arne <22494894+arnehude@users.noreply.github.com>
Date: Thu, 5 Dec 2024 10:18:03 +0100
Subject: [PATCH] Update faq.mdx to reflect relay usage (#255)

* Update faq.mdx to reflect relay usage

Updated the Documentation to account for the relay service. May be used in a peer-to-peer setting, where one peer acts as a router.

* Fixed Typo
---
 src/pages/about-netbird/faq.mdx | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/src/pages/about-netbird/faq.mdx b/src/pages/about-netbird/faq.mdx
index 0bc57e5a..9f46f2b5 100644
--- a/src/pages/about-netbird/faq.mdx
+++ b/src/pages/about-netbird/faq.mdx
@@ -36,6 +36,13 @@ Below is the list of NetBird hosted endpoints and ports they listen to:
         * `nslookup turn.netbird.io`
     * 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
+  * **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.
+
+
 
 ## Why and what are the anonymous usage metrics?