补充内网穿透说明 (#102)

docs/en_US/guide/nat.md

@@ -3,7 +3,7 @@ outline: deep
 ---
 # NAT Traversal Configuration
 
-Nezha Server Monitoring includes built-in NAT traversal capabilities, allowing users to expose internal services running on an Agent (such as home OpenWrt routers or NAS devices) to the public internet. This functionality facilitates remote access and is currently limited to supporting HTTP protocol traversal.
+Nezha Server Monitoring includes built-in NAT traversal capabilities, allowing users to expose internal services running on an Agent (such as home OpenWrt routers or NAS devices) to the public internet. This functionality facilitates remote access and is currently limited to supporting plain HTTP traversal.
 
 ## Preparation
 
@@ -23,8 +23,8 @@ If your Dashboard server uses tools like the aaPanel or similar management platf
 2. Click the "Add" button and provide the following required details:
    - **Name**: Assign a custom name to this traversal setup, for example, `OpenWrt Login Page`.
    - **Agent ID**: Input the ID of the Agent for which traversal is needed.
-   - **Internal Service Address**: Specify the internal service address that requires traversal, in the `IP:port` format, such as `127.0.0.1:80`.
-   - **Domain Name**: Enter the previously configured public domain name, like `service-1.example.com`.
+   - **Local service**: Specify the internal service address that requires traversal, in the `IP:port` format, such as `127.0.0.1:80`.
+   - **Bind hostname**: Enter the previously configured public domain name, such as `service-1.example.com`. If a non-standard port is used by Dashboard (e.g. default `8008`), be sure to include it as well.
 3. After filling in the details, click the "Add" button and wait for the traversal setup to activate.
 4. Test the configuration by accessing `http://service-1.example.com` to ensure the internal service on the Agent is successfully accessible.
 

docs/en_US/guide/servers.md

@@ -41,11 +41,12 @@ It is available for both Linux and Windows and supports Ctrl+Shift+V for pasting
 If the connection fails, refer to [Real-Time Channel Disconnection/Online Terminal Connection Failure](/en_US/guide/q4.html).
 
 ## FM
+
 Added in Dashboard v0.19.1 / Agent v0.19.0. A pseudo file manager embedded in WebShell, supports file download/upload, directory navigation and copying current path. Access it by clicking the blue button in the bottom-right corner of the WebShell.
 
 ## DDNS Functionality
 
-The DDNS functionality is suitable for servers with dynamic IPs. When the Agent reports a new IP, the Dashboard will automatically update the DNS records based on the configuration.
+The DDNS functionality is suitable for servers with dynamic IPs. When the Agent reports a new IP (every 10 minutes), the Dashboard will automatically update the DNS records based on the configuration.
 
 ### Why Use Nezha Monitoring's DDNS Functionality?
 

docs/guide/nat.md

@@ -3,7 +3,7 @@ outline: deep
 ---
 # 内网穿透功能配置
 
-哪吒服务器监控提供内置的内网穿透功能，允许用户通过设定 Dashboard 作为服务端，将运行在 Agent 上的内网服务（如家庭 OpenWrt 路由器、NAS 设备等）映射到公网上，便于外部访问。目前仅支持 HTTP 协议的穿透。
+哪吒服务器监控提供内置的内网穿透功能，允许用户通过设定 Dashboard 作为服务端，将运行在 Agent 上的内网服务（如家庭 OpenWrt 路由器、NAS 设备等）映射到公网上，便于外部访问。目前仅支持明文 HTTP 的穿透。
 
 ## 准备工作
 
@@ -24,7 +24,7 @@ outline: deep
    - **穿透名称**：为此穿透配置自定义一个名称，如`OpenWrt 登录页`。
    - **Agent ID**：填写需要进行穿透的 Agent 的 ID。
    - **内网服务地址**：填写需穿透的内网服务地址，格式为 `IP:端口`，例如 `127.0.0.1:80`。
-   - **绑定域名**：填写已准备的公网域名，如 `service-1.example.com`。
+   - **绑定域名**：填写已准备的公网域名，如 `service-1.example.com`。如果面板使用了非标准端口访问（比如默认的 `8008`），需要手动添加才可以生效。
 3. 完成填写后，点击“新增”按钮，等待穿透生效。
 4. 尝试访问 `http://service-1.example.com`，以验证是否成功映射至 Agent 上的内网服务。
 

docs/guide/servers.md

@@ -41,11 +41,12 @@ Linux 和 Windows 均可用，可使用 Ctrl+Shift+V 粘贴。
 连接失败请参考[实时通道断开/在线终端连接失败](/guide/q4.html)。
 
 ## FM
+
 Dashboard v0.19.1 / Agent v0.19.0 加入的新功能，是嵌入 WebShell 的一个伪文件管理器，提供文件下载和上传功能，也可以进行目录跳转或者复制路径。点击 WebShell 右下角的蓝色按钮就可以打开。
 
 ## DDNS 功能
 
-DDNS 功能适用于使用动态 IP 的服务器，当 Agent 上报了一个新的 IP，Dashboard 会根据配置自动更新 DNS 记录。
+DDNS 功能适用于使用动态 IP 的服务器，当 Agent 上报了一个新的 IP（10分钟一次），Dashboard 会根据配置自动更新 DNS 记录。
 
 ### 为什么我要使用哪吒监控的 DDNS 功能？