DNS records
Which DNS records you create to serve an application on Gigadrive Network, and who operates the gigadrive.app zone.
This page is a draft
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 | Not supported yet | 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
Not available yet
There is no verification record to publish and no target to point at, because Custom domains are not available. Any A, ALIAS, or CNAME instruction you find for Gigadrive Network today is guesswork. Gigadrive Network will publish the required record table when the feature ships.