dns failing on every use of flyctl - due to use of hardcoded resolver

Every time I use flyctl it runs a DNS lookup at the end that will always fail, as alternate DNS providers are blocked in this environment. TCP is redirected, but flyctl bakes in over UDP and does not allow a change or for that step to be skipped. It also has a very long timeout (way longer than is reasonable for a DNS pass/fail imo).

This makes it very frustrating to make the simplest changes - does anyone have a solution, or alternate method of deploying?

Hi… Try --dns-checks=false, if it’s during a fly deploy.

Hope this helps!

oh I missed that somehow in the docs - will give that a go next deploy; tysm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.