Q CLI Telemetry Not Reporting to Activity Dashboard Since 9/22

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 15.7.1 (24G231)

### Expected behaviour

Q CLI usage should be reported to the Q Activity Dashboard (https:xxxxxxx.com/amazonqactivitydashboard/main) showing chat sessions, tool usage, and other activity metrics.

### Actual behaviour

No activity has been recorded on the dashboard since 9/22/2025, despite active daily usage of Q CLI v1.17.1. Comprehensive diagnostics show DNS resolution issue where telemetry.us-east-1.amazonaws.com resolves to local router (192.168.4.1) instead of AWS infrastructure, preventing telemetry transmission.

```
[chat-transcript]
Based on the Q CLI documentation, the most recent version is **1.17.1**, released on **September 30, 2025**.

You can also check the changelog using the `/changelog` command in Q CLI to see the latest updates:

**Recent releases:**
- **1.17.1** (2025-09-30) - Added model description under `/model` command
- **1.17.0** (2025-09-29) - Major release with SSE support for MCP, `/reply` command, experimental checkpointing, context usage percentage, custom prompts, and various

.... The fact that 1.16.1 specifically fixed "Dashboard not updating after logging in" and your issue started around 9/22 (which aligns with those release dates) strongly suggests either:

1. **Regression introduced** - The fix didn't fully address the root cause or broke something else
2. **Environment-specific issue** - The fix works for most users but fails in certain network/auth configurations like yours
3. **Silent failure** - The telemetry is failing but not logging errors, making it invisible to both users and developers

Your comprehensive diagnostics report should definitely get their attention since it shows:
- Clear evidence of active usage
- Proper authentication
- The smoking gun DNS resolution issue
- Timeline correlation with the releases

The DNS resolution to your local router instead of AWS infrastructure is particularly damning evidence that something is fundamentally broken in the telemetry endpoint configuration or network path.

> q issue

[Tool uses: report_issue]

(...truncated)
```

### Steps to reproduce

1. Use Q CLI normally with chat sessions and tool usage
2. Check Q Activity Dashboard at xxxxxxxxxxx.com/amazonqactivitydashboard/main
3. Observe no activity recorded since 9/22/2025
4. Run DNS lookup on telemetry.us-east-1.amazonaws.com - resolves to local router instead of AWS IP
5. Attempt connection to telemetry endpoint - fails with timeout

### Environment

```yaml

[q-details]
version = "1.17.1"
hash = "b0ef39f91625c36c2ed6f065628e7165fae9012c"
date = "2025-09-30T22:01:25.726592Z (7d ago)"

[system-info]
os = "macOS 15.7.1 (24G231)"
chip = "Apple M2 Pro"
total-cores = 10
memory = "16.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
install-method = "toolbox"

[env-vars]
PATH = "/Users/USER/.local/bin:/Users/USER/.toolbox/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/USER/Library/Application Support/JetBrains/Toolbox/scripts:/Applications/Visual Studio Code.app/Contents/Resources/app/bin"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "org.tabby"

[chat-settings]

[chat-trusted_tools]
execute_bash=trusted
fs_write=trusted

[chat-failed_request_ids]
none

[chat-context]
current_profile=default
profile_context=none

files=none
```