Supported types
Fields per record
Every record has:Apex (root) records
Standard DNS doesn’t allow aCNAME at the apex (example.com itself). Brimble works around this:
- If you set a
CNAMEat@, Brimble stores it but synthesizes anArecord pointing at the edge so resolvers see something they can use. - In practice, set the apex record as
Aproxied to the edge, and setwwwasCNAMEtogateway.brimble.app.
Proxied vs not
A record marked proxied routes traffic through Brimble’s edge. Use proxied records to:- Get automatic TLS for the hostname.
- Hide the origin IP from public DNS.
- Apply edge features (rate limiting, caching, etc.).
- Mail records (
MX,TXTwith SPF/DKIM/DMARC), never proxy these. - Records pointing to non-Brimble services (SaaS verification, third-party hosts).
A and CNAME records can be proxied.
TTL guidelines
After making a change, raise the TTL back up to the long value once you’re confident.
Common patterns
Pointing the apex and www at the same project
Email through Google Workspace
Subdomain on another nameserver
api.example.com to a different DNS provider. Useful when one team controls the apex and another controls a subdomain.
Domain verification (Google, Stripe, GitHub, etc.)
@ (the apex) unless the provider says otherwise.
Manage records
In the dashboard, open the domain (under Domains in your account or under Domains on a project) and use the DNS tab to add, edit, or delete records. Each row shows type, host, value, TTL, and whether the record is proxied through Brimble’s edge.Verify a record
Limits
- A domain can hold many records, but a single host can only have one of each type (except
MX,NS, andTXT, which support multiple). - Record names must follow DNS label rules: lowercase letters, digits, dashes; max 63 characters per label, 253 for the full name.
- Proxied records must be
AorCNAME. Other types can’t be proxied.