# How to point a domain at a Quake AI resource

Source: https://docs.quake.ai/docs/network/how-to/point-domain-to-quake-ai
Markdown: https://docs.quake.ai/docs/network/how-to/point-domain-to-quake-ai.md

---

# 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.



Quake AI provides floating IP addresses for public workloads. Your registrar (Namecheap, Cloudflare, GoDaddy, and others) or a dedicated DNS host (Cloudflare DNS, Route 53 when used only as DNS, and similar) stores the `A` or `CNAME` records visitors query. The Console and CLI steps below show how to find the address to publish. The registrar steps show what to enter in the DNS host UI.



<PrerequisiteBlock methods={["console", "cli"]}>

- A [floating IP](/docs/network/how-to/allocate-floating-ips) allocated and associated with an application or reverse proxy instance
- Access to edit DNS records for the domain at your registrar or DNS host

</PrerequisiteBlock>

## 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](/docs/network/how-to/allocate-floating-ips) first.

## Get the public address on Quake AI

<MethodTabs>
<Method label="Console">

1. Open **Network** > **Floating IPs** and copy the floating IP value from the **ID/Floating IP** column for the row that matches your instance.
2. For an instance, open **Compute** > **Instances**, select the instance, and copy the address from the **Floating IP** column (private-network instance) or the **Fixed IP** column (public-network instance on `PublicEphemeral`).

</Method>
<Method label="CLI">

List floating IPs and their associated ports:

```bash
openstack floating ip list -f table -c "Floating IP Address" -c Port -c "Fixed IP Address"
```

Filter the list to a specific floating IP:

```bash
openstack floating ip list \
  --floating-ip-address FLOATING_IP_ADDRESS \
  -f value \
  -c "Floating IP Address"
```

The command prints the matching IPv4 address.

</Method>
</MethodTabs>

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`:

```text
www.example.com.  IN  A  203.0.113.50
```

TTL: 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](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/) |
| Namecheap | [How to configure DNS records](https://www.namecheap.com/support/knowledgebase/article.aspx/319/2237/how-can-i-set-up-an-a-address-record-for-my-domain/) |
| Squarespace Domains | [DNS records](https://support.squarespace.com/hc/en-us/articles/205812378) |
| GoDaddy | [Add an A record](https://www.godaddy.com/help/add-an-a-record-19238) |
| Gandi | [DNS records](https://docs.gandi.net/en/domain_names/operations/dns/index.html) |

## Verify propagation

From your workstation, query the hostname:

```bash
dig +short www.example.com A
```

The 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:

```bash
curl -I http://www.example.com
```

If the connection fails, confirm the instance security group allows inbound traffic on the port your application or reverse proxy listens on.

## Next steps

- [How to allocate floating IP addresses](/docs/network/how-to/allocate-floating-ips)
- [Edge reverse proxy template](/resources/iac-templates/edge-reverse-proxy)
- [How to create a VM on a public network](/docs/compute/how-to/create-vm-public-network)
- [How to put a CDN in front of a Quake AI workload](/docs/network/how-to/front-with-cdn)
- [How to self-host authoritative DNS on Quake AI](/docs/network/how-to/self-host-dns)
- [How to issue and auto-renew a TLS certificate with Let's Encrypt](/docs/network/how-to/lets-encrypt-certificate)
- [Floating IPs concepts](/docs/network/concepts/floating-ips)