Decided to play a bit again with this. Seems like the DNS isn't the issue, as when I try
curl -v https://js.prd.fusionapi.autodesk.com/hds/fusion360.json
I get,
* Trying [2600:9000:2486:d000:1f:7c10:5780:93a1]:443...
* Connected to js.prd.fusionapi.autodesk.com (2600:9000:2486:d000:1f:7c10:5780:93a1) port 443
* schannel: disabled automatic use of client certificate
* ALPN: curl offers http/1.1
* Recv failure: Connection was reset
* schannel: failed to receive handshake, SSL/TLS connection failed
* Closing connection
* schannel: shutting down SSL/TLS connection with js.prd.fusionapi.autodesk.com port 443
* Send failure: Connection was reset
* schannel: failed to send close msg: Failed sending data to the peer (bytes written: -1)
curl: (35) Recv failure: Connection was reset
So the ipv6 is resolving OK it seems. After some repeats, I do get a sporadic successes:
* Trying [2600:9000:2486:d000:1f:7c10:5780:93a1]:443...
* Connected to js.prd.fusionapi.autodesk.com (2600:9000:2486:d000:1f:7c10:5780:93a1) port 443
* schannel: disabled automatic use of client certificate
* ALPN: curl offers http/1.1
* ALPN: server accepted http/1.1
* using HTTP/1.1
> GET /hds/fusion360.json HTTP/1.1
> Host: js.prd.fusionapi.autodesk.com
> User-Agent: curl/8.4.0
> Accept: */*
>
* schannel: remote party requests renegotiation
* schannel: renegotiating SSL/TLS connection
* schannel: SSL/TLS connection renegotiated
< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 362
< Connection: keep-alive
< Date: Fri, 26 Apr 2024 20:23:17 GMT
< Last-Modified: Fri, 26 Apr 2024 20:22:41 GMT
< ETag: REDACTED
< x-amz-server-side-encryption: AES256
< x-amz-version-id: null
< Accept-Ranges: bytes
< Server: AmazonS3
< X-Cache: Miss from cloudfront
< Via: 1.1 18133da1ea724d113c4123fb3f20be9e.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: MIA3-P2
< X-Amz-Cf-Id: REDACTED
<
{
"id": "fusion360",
"name": "Fusion 360",
"previous_status": "degraded_performance",
"restore_delay": {
"commercial": 60,
"free": 720,
"trial": 120
},
"since_time": "2024-04-25T09:19:17.388-07:00",
"status": "operational",
"status_badge": "Operational",
"updated_at": "2024-04-25T09:19:17.388-07:00"
}* Connection #0 to host js.prd.fusionapi.autodesk.com left intact
If I try ipv4 only, it's rock solid the responses, which explains why it helps in my case to prioritize ipv4. I tested this with:
curl -4 -v https://js.prd.fusionapi.autodesk.com/hds/fusion360.json
Just wanted to post since from this info it seems it's not a DNS issue like I had previously thought.