DNS Provider Compatibility

To run a root domain (example.com, no www) on deploybase you need an ALIAS or ANAME record, because standard DNS forbids a CNAME at the zone apex and A records won’t work — deploybase’s CDN has no fixed IP. Subdomains (including www) are never a problem: a plain CNAME works at every provider.

Whether your root domain “just works” therefore depends on your DNS provider. This page lists what popular Dutch and German providers support, verified against each provider’s own documentation (last verified: July 2026 — capabilities change, check the linked docs for current state).

Two columns matter:

• Apex ALIAS — can you point the root domain at deploybase directly?
• HTTPS redirect — if not, the fallback is www as your canonical domain plus a provider-side redirect from the root to www. That redirect must answer over HTTPS, or visitors typing https://example.com get a certificate error.

Netherlands

Provider	Apex ALIAS	HTTPS redirect to www	Notes
TransIP	✅ “ALIAS-record”	✅ Free, auto Let’s Encrypt	Redirect SSL only for domains ≤42 characters; ALIAS not needed if you use it
Vimexx	✅ “ALIAS-record”	Not documented	ALIAS doesn’t work together with DNSSEC
Hostnet	❌	✅ Paid add-on (€0.50/mo)	Free forwarding is HTTP-only
Mijndomein	❌	✅ Paid add-on “Veilig doorsturen” (€2.50/yr)	Redirects without SSL can no longer be set up at all
Versio	❌	Not documented	Forwarding exists; docs don’t mention SSL
Antagonist	❌	Not documented	DirectAdmin-based DNS, no ALIAS record type
Openprovider	❌ Explicitly unsupported	❌ Explicitly HTTP-only	Docs state forwarding “works only from HTTP websites”

Germany

Provider	Apex ALIAS	HTTPS redirect to www	Notes
INWX	✅ “ALIAS”	❌ Redirect server can’t handle HTTPS	ALIAS limits DNSSEC functionality; use the ALIAS, not the redirect
IONOS	❌	✅ Docs list https→https support	Certificate handling on the source domain isn’t documented
Strato	❌	❌ Redirects work over HTTP only
netcup	❌	❌ HTTPS redirect needs a webhosting plan	Built-in CCP forwarding has no SSL
united-domains	❌	❌ Certificates can’t be combined with their forwarding
ALL-INKL	❌	Not documented	CNAME explicitly limited to subdomains like www
Hetzner DNS	❌	— No redirect service	Pure DNS hosting, no forwarding feature

What to do if your provider has no ALIAS

Pick whichever fits you best:

1. Use www as your canonical domain. A www CNAME works everywhere. Add the root redirect at your provider — but check the table above first: if the redirect is HTTP-only, visitors going to https://example.com directly will see a certificate error.
2. Let deploybase host your DNS (beta). Choose “Use deploybase nameservers” when adding the domain and delegate your nameservers to us once — the root domain then works regardless of what your provider supports, and SSL is automatic. Your domain stays registered where it is.
3. Move only your DNS. Your domain can stay registered where it is — pointing its nameservers at a DNS service that supports ALIAS/ANAME (see the ✅ rows above, or services like Route 53) gives you apex support without transferring the domain.

Never use an A record. There is no IP address you can point at — an A record will appear to work in your DNS panel but the site won’t resolve to deploybase, and a stale A record blocks SSL issuance. See Apex domains.

Your provider isn’t listed?

Look for a record type called ALIAS, ANAME, “CNAME flattening”, or “apex CNAME” in your DNS panel — pointing to the CNAME target shown in your domain’s DNS instructions (unique per domain, it looks like deploybase-d-….b-cdn.net). If it exists, your root domain works. If not, use the www fallback or managed DNS above. Found something we should add or correct? Let us know.