[GH-ISSUE #3772] [Feature Request] Resolves the domain name every time when connecting to the FRP server.

gitea-mirror commented

2026-05-05 13:56:15 -06:00

Owner

Copy link

Originally created by @rikka0w0 on GitHub (Nov 15, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3772

Describe the feature request

Some FRP servers use DDNS to update their IP addresses in their DNS record. Those servers don't have static IP addresses, and their IP address can change frequently.

Currently, frpc only resolves the domain name once when it starts. This behavior makes it unable to detect host IP changes afterward. If the host IP changes while the frpc is running, the connection will be interrupted, and frpc will still try to connect to the old IP address. I encountered this a few times. Restarting frpc locally re-establishes the channel.

I suggest making frpc resolve the domain name whenever it attempts to connect to the server.

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @rikka0w0 on GitHub (Nov 15, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3772 ### Describe the feature request Some FRP servers use DDNS to update their IP addresses in their DNS record. Those servers don't have static IP addresses, and their IP address can change frequently. Currently, frpc only resolves the domain name once when it starts. This behavior makes it unable to detect host IP changes afterward. If the host IP changes while the frpc is running, the connection will be interrupted, and frpc will still try to connect to the old IP address. I encountered this a few times. Restarting frpc locally re-establishes the channel. I suggest making frpc resolve the domain name whenever it attempts to connect to the server. ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:56:15 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:56:18 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Nov 15, 2023):

When the previously connected frps exits, frpc will connect to the new address, otherwise it will not make any changes.

@fatedier commented on GitHub (Nov 15, 2023): When the previously connected frps exits, frpc will connect to the new address, otherwise it will not make any changes.

gitea-mirror commented

2026-05-05 13:56:19 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Dec 16, 2023):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Dec 16, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified