rustdesk/doc.rustdesk.com
1
0
Fork 0
mirror of https://github.com/rustdesk/doc.rustdesk.com.git synced 2026-04-23 16:36:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

seo/geo

Browse Source
This commit is contained in:
rustdesk
2026-03-20 15:16:55 +08:00
parent b6655924d6
commit 1736869d5f
462 changed files with 1479 additions and 124 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
content/self-host/nat-loopback-issues/_index.en.md
View File

@@ -2,6 +2,8 @@
title: NAT Loopback issues
weight: 500
pre: "<b>2.5. </b>"
description: "Fix NAT loopback or hairpin NAT issues when self-hosting RustDesk behind a router. Learn why LAN clients may fail when using a public IP or domain and how to solve it with router settings, local DNS, or hosts file overrides."
keywords: ["rustdesk nat loopback", "rustdesk hairpin nat", "rustdesk local dns", "rustdesk hosts file", "rustdesk self-hosted domain issue", "rustdesk lan public ip problem"]
---
{{% notice note %}}
@@ -9,6 +11,8 @@ This explanation involves complex networking knowledge, we need your assistance
{{% /notice %}}
NAT loopback, also called hairpin NAT, becomes a problem when devices on the same LAN try to reach your self-hosted RustDesk server through its public IP address or domain name. This guide explains why that happens and how to fix it with router support, local DNS, or hosts file overrides.
For more details about NAT Loopback, please check the [Wikipedia](https://en.m.wikipedia.org/wiki/Network_address_translation#NAT_hairpinning) page.
When you're deploying RustDesk server on your home network or any other network environment that is behind a NAT firewall, the RustDesk server and your clients **MUST** either:
@@ -130,4 +134,3 @@ For example:
```text
192.168.11.20 rustdesk.example.com
```