You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for reporting this! We have confirmed the issue, and believe it's likely due to our recent upgrade of the node-libcurl dependency for the 2021.2.0 release, which changed what DNS resolver backend is being used.
We are looking into ways to address it, and hope to get it fixed as soon as possible.
Update: we have identified that it is indeed a regression from the update to node-libcurl that impacts all platforms and we are working with the maintainer to get a build out sometime tonight or tomorrow morning that doesn't use c-ares for DNS to fix the issue.
In the meantime we have pulled 2021.2 from the auto-update api to reduce the impact on users, for those who are impacted please download the previous release mentioned here.
Update: new build for node-libcurl is up, we are preparing a new patch release for Insomnia which is going into testing and will be released shortly. Thank you to everyone who was a part of making this happen. ❤️