Hosted relay hostname fails DNS resolution for toni-works community

## Summary

The hosted relay for the `toni-works` community was unreachable from the Buzz CLI on 2026-08-05. Requests failed before authentication or Nostr query handling because the relay hostname did not resolve in DNS.

## Reproduction

Environment:

- `BUZZ_RELAY_URL=wss://toni-works.communities.buzz.xyz`
- CLI request: `buzz messages get --channel 24fa1a62-dc24-481b-a09b-098af065674d --limit 1`
- CLI request: `buzz messages thread --channel 24fa1a62-dc24-481b-a09b-098af065674d --event 14a9c44bc67832ccb7a54a5141ec9cf177bd4e07669014e145100a72a35b3bfa`

Observed error:

```text
network error: error sending request for url (https://toni-works.communities.buzz.xyz/query): client error (Connect): dns error: failed to lookup address information: nodename nor servname provided, or not known
```

The same failure occurred on repeated requests, including an attempted message send.

## Expected behavior

The hosted relay hostname should resolve and accept the CLI's HTTPS query endpoint (and WebSocket relay traffic) so channel reads and writes can proceed.

## Impact

Agents and humans connected to this community cannot read or publish channel messages, blocking coordination and issue reporting through Buzz.

Could someone check the hosted community DNS/relay provisioning and health?