{"version":"2.1.300","anchor":"gateway-login-dns-checks-share-a-timeout-budget","canonical_anchor":"gateway-login-dns-checks-share-a-timeout-budget","heading":"Gateway login gives a clear error when host or proxy lookups are too slow","tier":"notice","area":"Auth","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/gateway-login-dns-checks-share-a-timeout-budget","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Gateway login gives a clear error when host or proxy lookups are too slow\n\nGateway login now limits how long it waits to look up the gateway host and the HTTP proxy, and says which one could not be resolved in time\n\n**What**\n\nDuring gateway login, Claude Code looks up the address of the gateway host and of your configured HTTP proxy. Before, only one later step of login had a time limit.\n\nBoth lookups can now share an overall time limit. If they run out of time, the error names the one that failed, either the configured HTTP proxy or the gateway host. It says it could not be resolved within a given number of seconds and asks you to try again.\n\n**Why**\n\nSlow network name lookups during gateway login now end with a plain message saying what to retry.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}