Our application we run on Fly.IO uses node.js which has a default behavior of connecting to IPv6 addresses over IPv4 addresses when resolving a domain. Before today that has not been an issue as it can safely connect to IPv6 addresses however this morning it has been throwing EHOSTUNREACH errors when attempting to connect to an IPv6 address (aka No Route to Host). I have temporarily created a workaround by forcing node.js to prefer IPv4 addresses via NODE_OPTIONS. I think this is potentially related to the networking incident that was resolved this morning but even a restart of our servers did not fix this issue. This can be replicated by attempting the following ping command via ssh ping 2620:127:f00f:e:: where it will not ping (which is the AAAA record for store.myshopify.com) vs ping 23.227.38.74 is working (which is the A record for store.myshopify.com)
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.