Files
zeekayandHanzo Dev c824445f45 lux.cloud names every host it serves; the wildcard is gone
explore, api-explore and cdn.lux.cloud were answered only through *.lux.cloud,
which also answered admin, kms and s3.lux.cloud with a 404 after their own
records were deleted. The three served hosts now have records of their own.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-23 13:27:32 -07:00

80 lines
1.7 KiB
YAML

# lux-cloud.yaml — Cloudflare zone config for lux.cloud
# Zone ID: 6a015a77307b6b6b355fb69c4a3de548
# Exported from the live zone 2026-09-23; proxied A records name the AWS ingress (100.24.244.37).
---
zone: lux.cloud
zone_id: "6a015a77307b6b6b355fb69c4a3de548"
records:
- type: A
name: "api-explore"
content: "100.24.244.37"
proxied: true
comment: "AWS ingress"
- type: A
name: "api"
content: "100.24.244.37"
proxied: true
comment: "hanzo AWS balancer (was the LAN tunnel)"
- type: A
name: "cdn"
content: "100.24.244.37"
proxied: true
comment: "AWS ingress"
- type: A
name: "cloud"
content: "100.24.244.37"
proxied: true
comment: "hanzo AWS balancer (was the LAN tunnel)"
- type: A
name: "console"
content: "100.24.244.37"
proxied: true
comment: "hanzo AWS balancer (was the LAN tunnel)"
- type: A
name: "exchange"
content: "100.24.244.37"
proxied: true
comment: "hanzo AWS balancer (was the LAN tunnel)"
- type: A
name: "explore"
content: "100.24.244.37"
proxied: true
comment: "AWS ingress"
- type: A
name: "@"
content: "100.24.244.37"
proxied: true
comment: "hanzo AWS balancer (was the LAN tunnel)"
- type: A
name: "nodes"
content: "100.24.244.37"
proxied: true
comment: "hanzo AWS balancer (was the LAN tunnel)"
- type: A
name: "pay"
content: "100.24.244.37"
proxied: true
comment: "hanzo AWS balancer (was the LAN tunnel)"
- type: A
name: "tokens"
content: "100.24.244.37"
proxied: true
comment: "hanzo AWS balancer (was the LAN tunnel)"
- type: A
name: "www"
content: "100.24.244.37"
proxied: true
comment: "hanzo AWS balancer (was the LAN tunnel)"