DNS
Verify and point custom domains at your services.
Appentic uses standard DNS records to verify domain ownership and route traffic. You add the records at your own registrar or DNS provider, so Appentic never needs access to your DNS zone and you keep full control over your domain. Nothing about this is Appentic-specific: the records you're adding are the same kind you'd use with any other platform.
Subdomain (CNAME)
For subdomains like api.example.com, add a CNAME record pointing at the target shown in the Appentic dashboard:
api.example.com. CNAME <target>.appentic.app.This is the common case and it works on every DNS provider.
Apex domain (ALIAS / ANAME)
For apex domains like example.com, your DNS provider needs to support ALIAS, ANAME, or flattened CNAME records. Cloudflare, Route53, DNSimple, Namecheap Advanced DNS, and most other modern providers all do. The record looks like:
example.com. ALIAS <target>.appentic.app.If your provider doesn't support any flattening mechanism at the apex (which isn't valid DNS to begin with), the practical workaround is to point www.example.com at Appentic with a regular CNAME and set up an HTTP redirect from the apex to the www subdomain. Every provider can do that.
Verification
Once the record is in place, click Verify in the Appentic dashboard. Appentic polls your DNS and then provisions a TLS certificate once the hostname resolves correctly. This usually takes under a minute, but can be longer if your provider has a high TTL you haven't lowered.