How to point a domain at a Quake AI resource
Coming from another cloud?
▸AWS·Route53 Alias
This Quake AI feature maps to AWS’s Route53 Alias.
▸DigitalOcean·DNS Records
This Quake AI feature maps to DigitalOcean’s DNS Records.
▸Google Cloud·Cloud DNS
This Quake AI feature maps to Google Cloud’s Cloud DNS.
▸Hetzner·DNS
This Quake AI feature maps to Hetzner’s DNS.
How to point a domain at a Quake AI resource
Publish a hostname that resolves to a workload on Quake AI. Allocate a public address on the platform, then create an A or CNAME record at your domain registrar or DNS host. Quake AI does not host authoritative DNS for your domain.
Prerequisites
- ConsoleLogged in to the Quake AI console
- CLIOpenStack CLI installed and authenticated (
clouds.yamloropenrcsourced)
Windows: CLI examples use bash. Set up a Linux CLI environment on Windows before proceeding.
- A floating IP allocated and associated with an application or reverse proxy instance
- Access to edit DNS records for the domain at your registrar or DNS host
Choose the target address#
| Workload shape | Address to publish | Where to find it |
|---|---|---|
| Instance on a private network | The floating IP associated with the instance | Compute > Instances (Floating IP column) or Network > Floating IPs |
| Instance on a public network | The instance's public fixed IP | Compute > Instances (Fixed IP column on PublicEphemeral) |
| Reverse proxy | The floating IP associated with the reverse proxy instance | Compute > Instances or Network > Floating IPs |
If you have not allocated a floating IP yet, follow How to allocate floating IP addresses first.
Get the public address on Quake AI#
Record the IPv4 address. Quake AI floating IPs in current regions are IPv4. If you have an IPv6 address to publish, add a matching AAAA record at your DNS host using the same hostname.
Add the DNS record at your registrar#
At your domain's DNS host, create a record that points your hostname at the address from the previous section.
| Record type | Name field | Value field | When to use |
|---|---|---|---|
A | @ for apex (example.com) or a subdomain label (www, api) | The Quake AI floating IP or fixed public IP | Direct hostname-to-IP mappings |
CNAME | Subdomain label only | Another hostname that already has an A record | When your DNS host does not allow A records on the apex and you use a www CNAME pattern |
Example for www.example.com pointing at floating IP 203.0.113.50:
www.example.com. IN A 203.0.113.50TTL: start with 300 seconds (five minutes) while you test, then raise it after the record is stable.
Registrar documentation#
Each provider uses different UI labels. Use their DNS or nameserver documentation to add an A record:
| Provider | DNS record documentation |
|---|---|
| Cloudflare | Manage DNS records |
| Namecheap | How to configure DNS records |
| Squarespace Domains | DNS records |
| GoDaddy | Add an A record |
| Gandi | DNS records |
Verify propagation#
From your workstation, query the hostname:
dig +short www.example.com AThe command prints the Quake AI address you published. DNS caches respect TTL. If you see an old address, wait for the previous TTL to expire, or lower TTL before you change records.
Send a test HTTP or HTTPS request once DNS resolves:
curl -I http://www.example.comIf the connection fails, confirm the instance security group allows inbound traffic on the port your application or reverse proxy listens on.
Next steps#
Usage Guidelines
The sample code, software libraries, command line tools, proofs of concept, templates, and other related technology on this page (including any of the foregoing that is provided by Quake AI personnel) is provided to you as Quake AI Content under the Quake AI Customer Agreement, or the relevant written agreement between you and Quake AI (whichever applies). Do not use this Quake AI Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the Quake AI Content (such as sample code) as appropriate for production grade use based on your specific quality control practices and standards. Deploying Quake AI Content may incur Quake AI charges for creating or using Quake AI chargeable resources, such as running Compute instances or storing data in Object Storage. Your use is also subject to the Acceptable Use Policy.
For the full policy, see Usage Guidelines.
Last validated: 01.09.2026
See Also
How to self-host authoritative DNS on Quake AI
Shares: DNS, Floating IPs
How to Create a Network
Shares: DNS, Networks
How to host a static site on object storage
Shares: DNS, Networks
Network how-to guides
Shares: DNS, Floating IPs
How to put a CDN in front of a Quake AI workload
Shares: Floating IPs, Networks