From cb33c322ee630d0406d1cd24533db3cee6f2e764 Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Sat, 23 Aug 2025 11:11:20 +0800
Subject: [PATCH] Updated FAQ (markdown)

---
 FAQ.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/FAQ.md b/FAQ.md
index c1afafc..f5c352a 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -464,8 +464,11 @@ Here is how ChatGPT explains NAT hairping.
 Also we high recommend you deploy on cloud instance which make your life quite simple, here is an example.
 
 > User: Well, I DID deploy the server in intranet (LAN) but I also am using DNS and DID set up a DNS re-write to the LAN version of the Rustdesk server IP for intranet endpoints but I am still having these issues. I did #2 here: https://rustdesk.com/docs/en/self-host/nat-loopback-issues/, The NAT hairpinning *might* explain the lack of connectivity to an onsite endpoint that has VPN turned on. But it does not explain me being unable to remote control offsite endpoints from campus...
+>
 > ...
+>
 > ...
+>
 > User: I just migrated it to a Linode instance and redirected DNS and everything is good now. Thanks for your help!