{"version":"2.1.312","anchor":"telemetry-logs-egress-pause-now-probed-by-dns-look-ahead","canonical_anchor":"telemetry-logs-egress-pause-now-probed-by-dns-look-ahead","heading":"Usage logging checks DNS for the logs host before sending","tier":"notice","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/telemetry-logs-egress-pause-now-probed-by-dns-look-ahead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Usage logging checks DNS for the logs host before sending\n\nClaude Code now looks up its logs host in DNS before sending usage logs, and pauses and warns when the host cannot be found\n\n**What**\n\nClaude Code sends usage logs to a logs server. It now looks up that server's address first, in DNS, the system that turns a host name into an address (`logs_host_lookup`).\n\n- If DNS gives no address for the logs host (ENOTFOUND), sending pauses and the logs are dropped.\n\n- You get a warning, and it says whether the refusal was confirmed or not.\n\n- Before, there was only one record of a refused send and a fixed pause.\n\nThe same finding also notes two small changes. `rollback` was dropped from a list of token-check reasons, next to `stale` and `future_iat`. One call now passes `keys: process.stdin.isTTY === !0`, which is true when the input is an interactive terminal.\n\n**Why**\n\nOn a machine with no internet or in a locked-down setup, Claude Code makes fewer failed attempts to send logs and tells you plainly that it cannot reach the logs host.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}