DNS records
Which DNS records you create to serve an application on Gigadrive Network, for gigadrive.app URLs and for a domain you own.
Diese Seite ist ein Entwurf
You create no DNS records to serve an application on Gigadrive Network. Every generated URL lives in a zone the platform operates, so there is nothing to add at your registrar and nothing to keep in sync.
| Address | Records you create | Zone operator |
|---|---|---|
my-app.gigadrive.app | None | Gigadrive Network |
my-app-git-feature-login.gigadrive.app | None | Gigadrive Network |
my-app-abc12345.gigadrive.app | None | Gigadrive Network |
| A domain you own | TXT and CNAME | You |
Why there is nothing to add
A wildcard CNAME in the gigadrive.app zone sends every label under the apex to the edge. One of the Deployment URLs therefore resolves as soon as it is created, and whether it answers depends on the deployment behind it rather than on a record reaching a resolver. There is no propagation wait between a deployment finishing and its URL working.
Two things are worth knowing if you are filling in a security questionnaire. The zone is DNSSEC signed. And a CAA record at the apex restricts certificate issuance for the zone, including the wildcard, to Let's Encrypt, which SSL certificates covers in more detail.
Records for a domain you own
A custom domain needs a TXT record that proves you control the domain, and a record that sends traffic to Gigadrive Network. The console and the API list the exact names and values for your domain.
| Record | Name | Value | When |
|---|---|---|---|
TXT | _gigadrive-challenge | gigadrive-verification= plus token | Once per domain |
CNAME | The subdomain, for example shop | cname.gigadrive-dns.net | For each subdomain you attach |
ALIAS | @ | cname.gigadrive-dns.net | For the apex, such as example.com |
The TXT record verifies the whole domain for your organization, so attaching api.example.com after shop.example.com needs only its CNAME. Each verified domain has its own token. Leave the TXT record in place after verification.
Apex records at common providers
The apex cannot hold a CNAME, so it needs the flattening record your provider offers:
- Cloudflare: a
CNAMEat@is flattened automatically. Set its proxy status to DNS only, because a proxied record hides Gigadrive Network from the certificate authority. - DNSimple, NS1, and other providers with
ALIASorANAMErecords: use that record. - Amazon Route 53: its alias records only point at AWS resources, so they cannot target Gigadrive Network. Attach
www.example.cominstead and redirect the apex to it. - Providers without flattening: attach
www.example.cominstead and redirect the apex to it at your provider.
Records that block a domain
- Proxied records: a record behind a proxy, such as the Cloudflare orange cloud, never reaches Gigadrive Network. Switch it to DNS only.
- Leftover records: remove old
AandAAAArecords for the hostname. A mix of old and new addresses sends some visitors elsewhere. CAArecords: if the domain has any, one must allowletsencrypt.org. CAA records on a custom domain lists the parameters that still block issuance.