RexSystem1 voteoriginally by @SolunaCG on GitHub OP
Additional testing: the issue currently appears to be intermittent.
Initially, normal launches consistently failed with ERR_NAME_NOT_RESOLVED, while launches with AsyncDns disabled and with --host-resolver-rules succeeded immediately.
However, after further testing, normal launches are now also succeeding consistently without any additional flags.
So at this point I cannot confirm that disabling AsyncDns is a reliable fix or that AsyncDns itself is the root cause. The original DNS resolution failures were real, but the issue is currently no longer reproducible on my system.
I will update this issue if it happens again and I can reproduce it more reliably.
Thread
Comment by @SolunaCG
ERR_NAME_NOT_RESOLVED, while launches withAsyncDnsdisabled and with--host-resolver-rulessucceeded immediately. However, after further testing, normal launches are now also succeeding consistently without any additional flags. So at this point I cannot confirm that disablingAsyncDnsis a reliable fix or thatAsyncDnsitself is the root cause. The original DNS resolution failures were real, but the issue is currently no longer reproducible on my system. I will update this issue if it happens again and I can reproduce it more reliably.