[BUG] 在服务器内转移到另外一个srv解析的服务器报错

[BrGef]

Prerequisites

• I made sure I am running the latest development build
• I tried to look for similar issues before opening a new one
• I have set debugmessages=true in config to diagnose my issue
• I have redacted session tokens and passwords before attaching screenshots

Minecraft Version

1.21.11

Console Client Version

20260406-412

Expected Behavior

服务器内有/server survival指令，它的作用就是转移到另外一个服务器，当我使用后报错
查看了一下报错,发现转移后他没有用srv解析，实际area.silinthoakes.top也是srv解析，这就出现了failed: 不知道这样的主机

[MCC] 已成功加入服务器。
输入 '/quit' 离开服务器。
[DEBUG] Receive JoinGame
[DEBUG] CanSendMessage = False
[DEBUG] SendPlayerSession MessageUUID = f6f7c0a0-a780-4301-ac7a-95ee01ee9552, len(PublicKey) = 294, len(SignatureV2) = 512
▌BrGef加入了游戏
[DEBUG] Receive ChatUuid = Empty
[DEBUG] Receive DeclareCommands
[DEBUG] CanSendMessage = True
[DEBUG] Receive ChatUuid = f6f7c0a0-a780-4301-ac7a-95ee01ee9552
[DEBUG] CanSendMessage = True
[DEBUG] Receive DeclareCommands
[DEBUG] CanSendMessage = True
[DEBUG] chat command = server survival
[MCC] Initiating a transfer to: area.silinthoakes.top:25565
[DEBUG] CanSendMessage = False
[ERROR] Transfer to area.silinthoakes.top:25565 failed: 不知道这样的主机。

未连接至任何服务器。输入 '/help' 获得帮助。
或者敲击回车退出Minecraft Console Client。

Unhandled exception. System.Exception: Transfer failed and reconnection attempts exhausted.
---> System.Net.Sockets.SocketException (0x00002AF9): 不知道这样的主机。
at System.Net.Dns.GetHostEntryOrAddressesCore(String hostName, Boolean justAddresses, AddressFamily addressFamily, Nullable1 activityOrDefault) at System.Net.Dns.GetHostAddresses(String hostNameOrAddress, AddressFamily family) at System.Net.Sockets.Socket.Connect(String host, Int32 port) at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port) at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at MinecraftClient.Proxy.ProxyHandler.NewTcpClient(String host, Int32 port, Boolean login) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/Proxy/ProxyHandler.cs:line 98 at MinecraftClient.McClient.Transfer(String newHost, Int32 newPort) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/McClient.cs:line 437 --- End of inner exception stack trace --- at MinecraftClient.McClient.Transfer(String newHost, Int32 newPort) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/McClient.cs:line 508 at MinecraftClient.Protocol.Handlers.Protocol18Handler.HandlePlayPackets(Int32 packetId, Queue1 packetData) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/Protocol/Handlers/Protocol18.cs:line 3237
at MinecraftClient.Protocol.Handlers.Protocol18Handler.HandlePacket(Int32 packetId, Queue`1 packetData) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/Protocol/Handlers/Protocol18.cs:line 636
at MinecraftClient.Protocol.Handlers.Protocol18Handler.Updater(Object o) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/Protocol/Handlers/Protocol18.cs:line 309
at System.Threading.Thread.StartHelper.Callback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

Actual Behavior

服务器内转移到另一个服务器没有用srv解析

Steps to Reproduce the bug

Attach screenshot here (If applicable)

No response

Anythings that could help diagnosing the bug

Device

None

Operating System

None

Server Address (If applicable)

No response

[milutinke]

感谢你报告这个问题，我会修复它。

---

Thanks for reporting the issue, I'll fix it.

[milutinke]

@BrGef

你好，这个问题里 MCC 在 transfer 过程中没有做 SRV 解析的部分，我已经修复了。

请先尝试最新的开发版：
https://github.com/MCCTeam/Minecraft-Console-Client/releases/latest

不过我这边还不能完全确认最终连接是否正常，因为目前这个地址的 DNS 解析结果是这样的：

1. _minecraft._tcp.area.silinthoakes.top -> svip.frpee.com:16583
2. svip.frpee.com -> 127.0.0.1

修复之后，MCC 已经会按照 SRV 记录去连接解析后的目标地址了。现在剩下的失败看起来不像是 MCC 本身的问题，更像是外部 DNS 或服务器配置的问题。

麻烦你在本地手动检查一下解析结果。

Linux 或 macOS：

1. 运行：
   dig +short _minecraft._tcp.area.silinthoakes.top SRV
2. 再运行：
   dig +short svip.frpee.com A
3. 如果需要，也可以运行：
   dig +short svip.frpee.com AAAA

Windows：

1. 运行：
   nslookup -type=SRV _minecraft._tcp.area.silinthoakes.top
2. 再运行：
   nslookup svip.frpee.com

请把这些命令的输出发出来。

如果你那边 svip.frpee.com 解析到的是正常的公网 IP，那么问题可能和地区或 DNS 解析器有关。
如果你那边也解析到 127.0.0.1，那剩下的问题基本就是 DNS 或服务器配置本身，不是 MCC 了。

---

Hello, I have fixed the SRV resolution issue during transfer in MCC.

Please try the latest development build first:
https://github.com/MCCTeam/Minecraft-Console-Client/releases/latest

I cannot fully verify the final connection on my side because the target DNS currently resolves like this:

1. _minecraft._tcp.area.silinthoakes.top -> svip.frpee.com:16583
2. svip.frpee.com -> 127.0.0.1

After the fix, MCC now follows the SRV record and tries to connect to the resolved target. The remaining failure looks external to MCC.

Could you please check the DNS result on your side?

On Linux or macOS:

1. Run:
   dig +short _minecraft._tcp.area.silinthoakes.top SRV
2. Then run:
   dig +short svip.frpee.com A
3. If needed, also run:
   dig +short svip.frpee.com AAAA

On Windows:

1. Run:
   nslookup -type=SRV _minecraft._tcp.area.silinthoakes.top
2. Then run:
   nslookup svip.frpee.com

Please send the output of those commands.

If svip.frpee.com resolves to a real public IP on your side, then the issue may be resolver or region specific.
If it also resolves to 127.0.0.1, then the remaining problem is very likely with the DNS or server setup, not MCC.

[BrGef]

复

这是我解析的结果，路由器上是用的运营商分配的dns
F:\minecrft\Comm_client\Mcc>nslookup -type=SRV _minecraft._tcp.area.silinthoakes.top
Server: zte.home
Address: 192.168.200.1

Non-authoritative answer:
_minecraft._tcp.area.silinthoakes.top SRV service location:
priority = 5
weight = 0
port = 16583
svr hostname = svip.frpee.com

F:\minecrft\Comm_client\Mcc>
F:\minecrft\Comm_client\Mcc>nslookup svip.frpee.com
Server: zte.home
Address: 192.168.200.1

Non-authoritative answer:
Name: svip.frpee.com
Address: 111.231.4.226

[BrGef]

@BrGef

你好，这个问题中，MCC在传输过程中没有进行SRV解析的处理，我已经修复了这个错误。

请先尝试最新的开发版： https://github.com/MCCTeam/Minecraft-Console-Client/releases/latest

不过我这边还不能完全确认最终连接是否正常，因为目前这个地址的 DNS 解析结果是这样的：

1. _minecraft._tcp.area.silinthoakes.top -> svip.frpee.com:16583
2. svip.frpee.com -> 127.0.0.1

修复之后，MCC会按照SRV记录来连接解析后的目标地址。现在出现的故障似乎并非MCC本身的问题，而更有可能是外部DNS或服务器配置方面的问题。

麻烦你在本地手动检查一下解析结果。

Linux或macOS：

1. 运行： dig +short _minecraft._tcp.area.silinthoakes.top SRV
2. 重新运行： dig +short svip.frpee.com A
3. 如果需要，也可以运行： dig +short svip.frpee.com AAAA

Windows：

1. 运行： nslookup -type=SRV _minecraft._tcp.area.silinthoakes.top
2. 重新运行： nslookup svip.frpee.com

请把这些命令的输出发出来。

如果你那边解析得到的结果是正常的公网IP地址，那么问题很可能出在地区设置或DNS解析器上。如果你那边也解析得到svip.frpee.com这个结果，那问题就出在DNS设置或服务器配置方面了，与MCC无关。

您好，我已经解决了在MCC系统中进行传输时出现的SRV解析问题。

请先尝试最新的测试版本： 点击此处下载：https://github.com/MCCTeam/Minecraft-Console-Client/releases/latest

我无法确认自己这端的连接是否正常，因为目标DNS的解析结果如下：

1. _minecraft._tcp.area.silinthoakes.top -> svip.frpee.com:16583
2. svip.frpee.com -> 127.0.0.1

修复后，MCC会遵循SRV记录的指示，尝试连接到已确定的目标地址。其余的故障则似乎与MCC本身无关，属于外部问题。

请您检查一下您那边的DNS查询结果吧。

在 Linux 或 macOS 系统上：

1. 跑步： dig +short _minecraft._tcp.area.silinthoakes.top SRV
2. 然后运行： dig +short svip.frpee.com A
3. 如有需要，也可运行： dig +short svip.frpee.com AAAA

在Windows系统中：

1. 跑步： nslookup -type=SRV _minecraft._tcp.area.silinthoakes.top
2. 然后运行： nslookup svip.frpee.com

请将这些命令的执行结果发过来。

如果svip.frpee.com最终对应的是你这边使用的真实公共IP地址，那么问题很可能出在解析器或地域设置上。而如果它对应的是127.0.0.1，那么问题很可能出在DNS设置或服务器配置上，而非MCC的问题。

我用测试版本测试了一下发现正常解析了，但是又出现了另外一个问题
从加入服务器开始的报错日志
[MCC] 已成功加入服务器。
输入 '/quit' 离开服务器。
[DEBUG] Receive JoinGame
[DEBUG] CanSendMessage = False
[DEBUG] SendPlayerSession MessageUUID = ***, len(PublicKey) = 294, len(SignatureV2) = 512
▌BrGef加入了游戏
[DEBUG] Receive ChatUuid = Empty
[DEBUG] Receive DeclareCommands
[DEBUG] CanSendMessage = True
[DEBUG] Receive ChatUuid = ***
[DEBUG] CanSendMessage = True
[DEBUG] Receive DeclareCommands
[DEBUG] CanSendMessage = True
[DEBUG] chat command = server survival
正在解析area.silinthoakes.top...
已找到服务器svip.frpee.com:16583，域名：area.silinthoakes.top
[MCC] Initiating a transfer to: svip.frpee.com:16583
[DEBUG] CanSendMessage = False
[MCC] Connected to svip.frpee.com:16583
[DEBUG] Using transfer handshake intent for transferred login.
[DEBUG] 密钥和哈希值已生成：
[MCC] 检查会话...
正在请求sessionserver.mojang.com

Method: POST, RequestUri: 'https://sessionserver.mojang.com/session/minecraft/join', Version: 1.1, Content: System.Net } Content-Type: application/json; charset=utf-8

< No Content
将会话缓存保存到磁盘
从磁盘转换会话缓存：SessionCache.db
已加载会话：***
已加载会话：@out.com:
已加载会话：mc.silinthoakes.top:***
[MCC] Successfully transferred connection and logged in to svip.frpee.com:16583.
[ERROR] Transfer to svip.frpee.com:16583 failed: Console Reader thread is already running.

未连接至任何服务器。输入 '/help' 获得帮助。
或者敲击回车退出Minecraft Console Client。

Unhandled exception. System.IO.InvalidDataException: 无法处理传入的Transfer类型的数据包。(数据包ID：127，协议：774，登陆阶段：False，内部异常：System.Exception)。
---> System.Exception: Transfer failed and reconnection attempts exhausted.
---> System.InvalidOperationException: Console Reader thread is already running.
at ConsoleInteractive.ConsoleReader.BeginReadThread() in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/ConsoleInteractive/ConsoleInteractive/ConsoleInteractive/ConsoleReader.cs:line 54
at MinecraftClient.ClassicConsoleBackend.BeginReadThread() in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/ClassicConsoleBackend.cs:line 38
at MinecraftClient.McClient.Transfer(String newHost, Int32 newPort) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/McClient.cs:line 460
--- End of inner exception stack trace ---
at MinecraftClient.McClient.Transfer(String newHost, Int32 newPort) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/McClient.cs:line 512
at MinecraftClient.Protocol.Handlers.Protocol18Handler.HandlePlayPackets(Int32 packetId, Queue1 packetData) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/Protocol/Handlers/Protocol18.cs:line 3249 at MinecraftClient.Protocol.Handlers.Protocol18Handler.HandlePacket(Int32 packetId, Queue1 packetData) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/Protocol/Handlers/Protocol18.cs:line 648
--- End of inner exception stack trace ---
at MinecraftClient.Protocol.Handlers.Protocol18Handler.HandlePacket(Int32 packetId, Queue`1 packetData) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/Protocol/Handlers/Protocol18.cs:line 680
at MinecraftClient.Protocol.Handlers.Protocol18Handler.Updater(Object o) in /home/runner/work/Minecraft-Console-Client/Minecraft-Console-Client/MinecraftClient/Protocol/Handlers/Protocol18.cs:line 309
at System.Threading.Thread.StartHelper.Callback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

[milutinke]

@BrGef 你好，请用客户端的最新版本再试一次，这个问题应该已经修复了。很遗憾，我这边无法连接到服务器，所以没法替你验证。感谢你反馈这个问题。

https://github.com/MCCTeam/Minecraft-Console-Client/releases/tag/20260408-419

[BrGef]

应该

ok现在测试正常了