{"version":"2.1.281","anchor":"managed-settings-gateway-refuses-names-that-resolve-to-publi","canonical_anchor":"managed-settings-gateway-refuses-names-that-resolve-to-publi","heading":"Managed-settings gateway refuses names that resolve to public addresses","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/managed-settings-gateway-refuses-names-that-resolve-to-publi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Managed-settings gateway refuses names that resolve to public addresses\n\nManaged settings fetched through a cloud gateway are refused, without retrying, if the gateway's name resolves to a public address\n\n**What**\n\nManaged settings are settings an organisation pushes to Claude Code. When they are fetched through a cloud gateway, Claude Code now checks the address that the gateway's name resolves to. If that address is public, the request is not sent and the fetch stops without retrying.\n\nThe new error kind is `gateway_public_address`, with the text \"Cloud gateway connection outside the network it was checked on\". It also has a plain description telling you that the gateway's name resolved to a public address.\n\n**Why**\n\nIf your organisation delivers settings through a gateway, this error means the gateway's name pointed at a public address. Because Claude Code does not retry, you get the error at once instead of repeated attempts.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}