zeekayandHanzo Dev
c0f5037b0f
k8s/dns globs *.yaml, so this directory was syncing seven zones it does not own. hanzo/universe and zoo/universe glob their own zone dirs the same way, which means two scripts held write authority over one zone and the last one run decided what the zone said. Nothing is lost by dropping them here. hanzo-id and hanzo-network were byte-identical to their copies in hanzo/universe. hanzo-ai there is the newer file: reconciled against live DNS on 2026-07-26 and carrying the note that a proxied:false record applied over a live proxied host publishes the origin. zoo-network and zoo-exchange were byte-identical to zoo/universe's, and its zoo-ngo is a superset -- the donate CNAME and the *.web3.zoo.ngo Universal-SSL notes exist only there. zoo.cloud had no copy under zoo/universe, so it moves rather than goes. Co-authored-by: Hanzo Dev <[email protected]>
79 lines
2.0 KiB
YAML
79 lines
2.0 KiB
YAML
# zoo-cloud.yaml — Cloudflare zone config for zoo.cloud
|
|
# Zone ID: 5f505170d0c1aedfee20dd20c2eeb413
|
|
# Source of truth for zoo.cloud DNS records
|
|
#
|
|
# The .cloud zones had no file here at all, which is how exchange.zoo.cloud came
|
|
# to be a host with an Ingress, a certificate and a green CD sync and no way to
|
|
# reach it: this zone has no wildcard, so the name simply did not resolve. There
|
|
# is nothing in an Ingress that creates a record — no external-dns runs on this
|
|
# cluster — so a new .cloud host is not live until it appears below AND in
|
|
# Cloudflare.
|
|
#
|
|
# exchange -> 134.199.138.27 is lux-system/hanzo-ingress, the lux-k8s
|
|
# LoadBalancer, the same address exchange.lux.cloud points at. Unproxied, like
|
|
# its Lux counterpart: the exchange-api sends its own CORS headers and an edge
|
|
# in front of it is one more thing that can write them a second time.
|
|
---
|
|
zone: zoo.cloud
|
|
zone_id: "5f505170d0c1aedfee20dd20c2eeb413"
|
|
|
|
records:
|
|
- type: A
|
|
name: admin
|
|
content: "129.212.164.5"
|
|
proxied: true
|
|
|
|
- type: A
|
|
name: api
|
|
content: "209.38.118.103"
|
|
proxied: true
|
|
|
|
- type: AAAA
|
|
name: api
|
|
content: "2604:a880:4:1d0:0:2:9994:3000"
|
|
proxied: true
|
|
|
|
- type: A
|
|
name: console
|
|
content: "129.212.164.5"
|
|
proxied: false
|
|
|
|
- type: A
|
|
name: exchange
|
|
content: "134.199.138.27"
|
|
proxied: false
|
|
|
|
- type: A
|
|
name: kms
|
|
content: "129.212.164.5"
|
|
proxied: false
|
|
|
|
# mpc.zoo.cloud is served by lux-mpc on the lux cluster, exactly like
|
|
# mpc.zoo.network and mpc.pars.network — one MPC deployment answering for
|
|
# every org rather than one per cluster. Unproxied, because that ingress
|
|
# terminates TLS itself.
|
|
- type: A
|
|
name: mpc
|
|
content: "134.199.138.27"
|
|
proxied: false
|
|
|
|
- type: A
|
|
name: pay
|
|
content: "129.212.164.5"
|
|
proxied: true
|
|
|
|
- type: A
|
|
name: s3
|
|
content: "129.212.164.5"
|
|
proxied: false
|
|
|
|
- type: CNAME
|
|
name: www
|
|
content: "web3.zoo.ngo"
|
|
proxied: true
|
|
|
|
- type: A
|
|
name: zoo.cloud
|
|
content: "134.199.138.27"
|
|
proxied: true
|