mirror of
https://github.com/rustdesk/rustdesk.git
synced 2026-03-02 19:26:56 -05:00
When a domain name has both IPv4 and IPv6 addresses, it may fail to connect to the relay network. #3381
Labels
No labels
bug
documentation
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
question
unreproducible
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rustdesk-rustdesk#3381
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @LingluoYusa on GitHub (Apr 17, 2025).
Bug Description
My home network and the relay server both support IPv4 and IPv6. When accessing using a domain name with a port, it shows a "not ready" message. However, accessing directly with the IPv4 address works fine.
How to Reproduce
By adding both A and AAAA records to a domain and using the domain with a port in the ID relay service for connection, if the server has not opened the corresponding port for IPv6 requests but has opened it for IPv4, the connection will fail when the domain resolves to IPv6 first.
Expected Behavior
If the domain resolves to IPv6 first and only the corresponding IPv4 port is open, the connection will fail. In this case, the system should attempt to connect using the A record (IPv4) after the AAAA record (IPv6) connection fails.
Operating system(s) on local (controlling) side and remote (controlled) side
Windows 11 => Windows 11
RustDesk Version(s) on local (controlling) side and remote (controlled) side
1.3.9 => 1.3.9
Screenshots
Additional Context
No response
@LingluoYusa commented on GitHub (Apr 17, 2025):
This bug can also be reproduced on Ubuntu.
@rustdesk commented on GitHub (Apr 17, 2025):
#763