[GH-ISSUE #2992] via a http proxy, direct ip works, but not a dns name

gitea-mirror commented

2026-05-05 13:32:22 -06:00

Owner

Copy link

Originally created by @bbbhere on GitHub (Jun 24, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2992

Bug Description

As the subject suggest, I can't connect a server by its dns name but the ip works.

frpc Version

0.43.0

frps Version

0.40.0

System Architecture

server linux/armv8, client windows/amd64

Configurations

no special

Logs

log of http-procy(clash)
time="2022-06-24T11:28:51+08:00" level=warning msg="[TCP] dial load-balance (match DomainSuffix/the-domain-name) to the-domain-name:27000 error: can not connect remote err code: 403"
time="2022-06-24T11:29:00+08:00" level=warning msg="[TCP] dial load-balance (match DomainSuffix/the-domain-name) to the-domain-name:27000 error: can not connect remote err code: 403"
time="2022-06-24T11:29:11+08:00" level=warning msg="[TCP] dial load-balance (match DomainSuffix/the-domain-name) to the-domain-name:27000 error: can not connect remote err code: 403"
time="2022-06-24T11:29:52+08:00" level=info msg="[TCP] my-clash-proxy-ip:11657 --> the-ip-of-domain-name:27000 match Match() using load-balance[http]"

log of frpc fail
2022/06/24 12:00:26 [W] [service.go:128] login to server failed: EOF
2022/06/24 12:00:36 [W] [service.go:128] login to server failed: EOF

log of frpc success
2022/06/24 12:01:35 [I] [service.go:349] [89f5c1f5d08b9d5f] login to server success, get run id [89f5c1f5d08b9d5f], server udp port [0]
2022/06/24 12:01:35 [I] [proxy_manager.go:144] [89f5c1f5d08b9d5f] proxy added: [test_tcp_0 test_tcp_1]
2022/06/24 12:01:35 [I] [control.go:181] [89f5c1f5d08b9d5f] [test_tcp_0] start proxy success
2022/06/24 12:01:35 [I] [control.go:181] [89f5c1f5d08b9d5f] [test_tcp_1] start proxy success

Steps to reproduce

...

Affected area

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

Originally created by @bbbhere on GitHub (Jun 24, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2992 ### Bug Description As the subject suggest, I can't connect a server by its dns name but the ip works. ### frpc Version 0.43.0 ### frps Version 0.40.0 ### System Architecture server linux/armv8, client windows/amd64 ### Configurations no special ### Logs log of http-procy(clash) time="2022-06-24T11:28:51+08:00" level=warning msg="[TCP] dial load-balance (match DomainSuffix/***the-domain-name***) to ***the-domain-name***:27000 error: can not connect remote err code: 403" time="2022-06-24T11:29:00+08:00" level=warning msg="[TCP] dial load-balance (match DomainSuffix/***the-domain-name***) to ***the-domain-name***:27000 error: can not connect remote err code: 403" time="2022-06-24T11:29:11+08:00" level=warning msg="[TCP] dial load-balance (match DomainSuffix/***the-domain-name***) to ***the-domain-name***:27000 error: can not connect remote err code: 403" time="2022-06-24T11:29:52+08:00" level=info msg="[TCP] ***my-clash-proxy-ip***:11657 --> ***the-ip-of-domain-name***:27000 match Match() using load-balance[http]" log of frpc fail 2022/06/24 12:00:26 [W] [service.go:128] login to server failed: EOF 2022/06/24 12:00:36 [W] [service.go:128] login to server failed: EOF log of frpc success 2022/06/24 12:01:35 [I] [service.go:349] [89f5c1f5d08b9d5f] login to server success, get run id [89f5c1f5d08b9d5f], server udp port [0] 2022/06/24 12:01:35 [I] [proxy_manager.go:144] [89f5c1f5d08b9d5f] proxy added: [test_tcp_0 test_tcp_1] 2022/06/24 12:01:35 [I] [control.go:181] [89f5c1f5d08b9d5f] [test_tcp_0] start proxy success 2022/06/24 12:01:35 [I] [control.go:181] [89f5c1f5d08b9d5f] [test_tcp_1] start proxy success ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others