Domains and DNS

Lumin Shield ↗Open panel ↗

TXT verification and directing traffic through Lumin.

Verify domain ownership

Open the route details. The panel provides the required TXT record name and value. Add those exact values to your DNS zone. For mc.example.com, the verification name is _shield.mc.example.com.

Use the token from your own panel, not an example or another organisation.

Run verification after saving the record. DNS changes can take time. If verification fails, check the full record name, its value and the authoritative name servers.

Configure ingress

The route's DNS instructions provide the Lumin ingress host and port. Apply those records. TXT proves ownership but does not direct player traffic.

Do not point the player-facing domain directly at your backend. For a non-default port, use an SRV record when instructed by the panel.

Using the API

• GET /v1/orgs/{org}/routes/{id}/dns - current DNS instructions.
• POST /v1/orgs/{org}/routes/{id}/verify - verify ownership.

Verification responses contain domains, txtRecord and txtRecords. Each domain has its own verified state. Only verified domains can be deployed for protection.