Hi Fly team!
I was excited to try connecting on-prem machines via wireguard to the fly private network. I got it working but it required some extra workarounds because the peername._peer.internal hostname is not compliant with RFC which allows for “_” in the URL but not in the domain name. As a result, a lot of common HTTP libraries along with curl and wget will raise a “URL violates RFC 2396” error.
Our workaround is to manually resolve the IPv6 address and pass in IPv6 as the URL, e.g., “https://[#{ip_address}]:8080”.
Is there a technical reason for the “_” in “_peer”? Could a second DNS entry be added without the underscore?
Thanks Fly team!
Kindly,
John