claudetools/.claude/memory/reference_cloudflare_access.md at 20d8b29a36926bbc2da0889470de5d4a61da9b4b

Files

Mike Swanson 6e1c65877f sync: auto-sync from GURU-5070 at 2026-06-15 11:20:33

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-15 11:20:33

2026-06-15 11:20:56 -07:00

1.3 KiB

Raw Blame History

name, description, metadata

name

description

metadata

reference-cloudflare-access

Where the Cloudflare API credentials live (SOPS vault) — azcomputerguru.com DNS is on Cloudflare, not the IX nameservers

type
reference

Cloudflare API access is in the SOPS vault at services/cloudflare.sops.yaml (account "Mike@azcomputerguru.com Account", account_id 44594c346617d918bd3302a00b07e122). Fields under credentials:

api_token_full_account — full-account token (solitary-rain-773d, added 2026-05-10, expires 2027-05-10)
api_token_full_dns — full DNS-edit token (use this for DNS record changes)
api_token_legacy — legacy token
zone_id_azcomputerguru = 1beb9917c22b54be32e5215df2c227ce

azcomputerguru.com DNS is hosted on Cloudflare (ns mckinley/amir.ns.cloudflare.com), NOT the IX/cPanel nameservers (ns1/ns2.acghosting.com) that most CLIENT domains use. So azcomputerguru.com zone edits go through the Cloudflare API, not whmapi1. Pattern: curl -H "Authorization: Bearer <api_token_full_dns>" https://api.cloudflare.com/client/v4/zones/<zone_id>/dns_records. (Used 2026-06-15 to add the cross-domain DMARC report-authorization record cryoweave.com._report._dmarc.azcomputerguru.com TXT "v=DMARC1;" so client DMARC reports can be sent to rua@azcomputerguru.com.) See reference_ix_server_access for client-domain DNS (cPanel).

1.3 KiB Raw Blame History

1.3 KiB

Raw Blame History