Connect your domain at IONOS
Add the certificate and www records in IONOS DNS and forward your root domain, since the IONOS DNS panel has no ALIAS records.
Provider steps checked November 18, 2026. Provider dashboards change; if a button has moved, the official help links at the bottom have the current wording.
You’ll add two or three records in your IONOS account: one that proves you own the domain, and the ones that point it at your site. It takes about 10 minutes, it can be undone, and it doesn’t touch your email.
Your Staticbot deployment page shows the exact values to paste, with a copy button next to each, and checks whether IONOS is already answering with them. Keep it open next to this guide.
Before you start
- A CNAME can’t share its name with A, AAAA, MX or TXT records. Delete any A or AAAA record on www before adding the CNAME.
Open the DNS records at IONOS
- Log in to IONOS and open Domains & SSL.
- Click the gear icon under Actions next to your domain and choose DNS.
- Click Add record and choose the type.
Host name and Points to are IONOS’s names for the two boxes you fill in. Type only the part before your domain (for example www). IONOS adds the domain itself.
Server-rendered app hosted on Cloudflare? Its deployment page lists TXT records and a CNAME on www pointing at apps.staticbot.app instead of the records below. Add them in the same form, with the same Host name rule.
Step 1: Add the certificate record
This record lets Amazon issue the HTTPS certificate for your domain. It doesn’t change where your site or email points. Add one record per certificate record shown on the deployment page:
Save, then go back to the deployment page and click Check my records. Staticbot asks IONOS’s own servers, so you see the answer within seconds. Once it shows Found, the certificate is usually issued within a few minutes.
Step 2: Point your domain at your site
The deployment page shows these records once the certificate is issued. If your site lives on a subdomain such as app.yourdomain.com, you only add one CNAME for it.
The IONOS DNS panel has no ALIAS record for the domain itself, so yourdomain.com (without www) can’t point at your site directly.
- Point www at your site with the CNAME record Staticbot shows.
- Forward the root: Domains & SSL → your domain → Adjust Destination → Domain Forwarding, use an HTTP redirect to https://www.yourdomain.com.
- If https://yourdomain.com must work too, change nameservers to Staticbot instead (see below).
For www.yourdomain.com:
Check it worked
The deployment page checks each record and tells you what it sees: Found, Not found yet, Wrong value, or Domain typed twice (the domain was typed into the Host name box). Most records show up within a minute. Your browser may keep showing the old page for a while after that; a private window shows the new one sooner.
Working with an AI agent connected to Staticbot? Ask it whether your DNS records are live; it runs the same check.
Common problems at IONOS
- IONOS won’t create the CNAME
- Another record uses the same host name. Delete the A, AAAA or old CNAME on that name first.
Make the domain itself work: change nameservers
Instead of adding records, you can point the domain’s nameservers at Staticbot. You then add no records at all: the certificate and the site, the domain itself included, are set up automatically. IONOS can’t point the domain itself at your site, so this is the way to make yourdomain.com work, not only www.
It’s the right choice when you don’t use the domain for anything else yet: no email on it, no other subdomains. The deployment page recommends it in that case. If the domain has email, Staticbot copies the email records it can see on the domain itself before you switch; records on other names (such as blog.yourdomain.com or email signing keys) have to be re-created, so adding records is usually the safer route there. The deployment page only offers the switch when it’s safe to.
At IONOS:
Find the domain, click the gear icon under Actions and choose Name Server. Click Use Custom Name Servers, enter the Staticbot nameservers in Name Server 1–4 and save. Turn off DNSSEC first if it is on.
More about what moves and what to check: changing nameservers.
