Two ways to connect
Automatic 3 providers
Your user pastes an API token or access key from their DNS provider. Cnamio reads the zone, creates only the records you asked for and discards the credential when the request ends.
- Cloudflare
- Hostinger
- Amazon Route 53
Guided every other provider
The connect window shows each record with its type, name, value and TTL and a copy button. Your user adds them in their own DNS panel; Cnamio keeps checking until they are live.
- Registro.br
- HostGator
- KingHost
- Locaweb
- Umbler
- GoDaddy
- any other provider
Either way your backend receives the same signed domain.added webhook once every required record is live, with setup_type set to automatic or manual.
How a provider becomes automatic. We list a provider here only after completing a real connection on a real zone through its official API, and checking that the rest of the zone was left exactly as it was. Until then it stays guided.
How the provider is detected
Cnamio looks up the domain's authoritative nameservers and matches them against known provider patterns. Where the domain was bought does not matter: a domain registered at one company with its DNS hosted at Cloudflare is treated as Cloudflare, because that is where the records have to be created.
Every nameserver has to belong to the same provider. A mixed or unknown set is treated as "other provider" and gets generic steps that work in any DNS panel, never a guess. Detection only decides the wording and whether a token can be offered; the records shown and the final verification do not depend on it.
The DNS zone is found the same way, so public suffixes such as .com.br and multi-level names work: for agenda.meustudio.com.br in the zone meustudio.com.br, your user is asked to create the name agenda.
Automatic setup
In the connect window your user sees the provider that was found and a field for the credential, with the steps to create it. From a backend or an agent, pass it to POST /connect/automatic. Then, in one request:
- Cnamio reads the zone with the credential.
- It compares the records you asked for with what already exists. If something is in the way, nothing is written and the user sees the conflict.
- It creates only the requested records.
- The credential is discarded. It is never written to disk, a database or a log.
- Propagation is checked on every authoritative nameserver until the records are live, and your backend receives the webhook.
A user who prefers not to paste a credential can always choose "I'd rather copy the records manually" and follow the guided steps.
Cloudflare Automatic
Credential: an API token that can edit DNS for the one zone.
- In the Cloudflare dashboard, open My Profile → API Tokens.
- Click Create Token and pick the "Edit zone DNS" template.
- Under Zone Resources, choose only this domain.
- Create the token, copy it and paste it in the connect window.
CNAME records are created as DNS only (not proxied). The token can be deleted as soon as the connection is made.
Hostinger Automatic
Credential: an API token from hPanel.
- In Hostinger hPanel, open Account → API.
- Generate a new token.
- Copy the token and paste it in the connect window.
The token can be deleted in hPanel as soon as the connection is made.
Amazon Route 53 Automatic
Credential: the access key ID and secret access key of an IAM user made for this, limited to the hosted zone. Temporary keys (ASIA…) are not accepted.
- In the AWS console, open IAM → Users → Create user, without console access.
- Allow it to edit only this Route 53 zone:
ListHostedZonesByName,ListResourceRecordSetsandChangeResourceRecordSets. - Under Security credentials, create an access key and paste its ID and secret in the connect window.
Use a policy that only allows creating records, and only in one zone. List the record types your application asks for (here, a CNAME and an ownership TXT):
{
"Version": "2012-10-17",
"Statement": [
{ "Effect": "Allow", "Action": "route53:ListHostedZonesByName", "Resource": "*" },
{ "Effect": "Allow", "Action": "route53:ListResourceRecordSets",
"Resource": "arn:aws:route53:::hostedzone/ZONE_ID" },
{ "Effect": "Allow", "Action": "route53:ChangeResourceRecordSets",
"Resource": "arn:aws:route53:::hostedzone/ZONE_ID",
"Condition": { "ForAllValues:StringEquals": {
"route53:ChangeResourceRecordSetsActions": ["CREATE"],
"route53:ChangeResourceRecordSetsRecordTypes": ["CNAME", "TXT"]
} } }
]
}
Route 53 itself refuses a CREATE for a record that already exists, so an existing record cannot be overwritten.
Guided setup
For every other provider, and whenever a user prefers not to use a credential, the window shows what to create:
- Each record with type, name, value and TTL (and priority for MX), each field with its own copy button.
- The name is relative to the zone (
shop, notshop.customer.com), which is what most DNS panels ask for. - After "I've added the records", the window waits and checks. Your user can close it: the connection continues on its own for up to 72 hours.
Public step-by-step guides for Registro.br, Hostinger, Locaweb, HostGator and KingHost, Cloudflare and GoDaddy, in English, Portuguese and Spanish, and a free CNAME checker that reads the authoritative nameservers. To see what your users would see for a given domain, try the live demo.
When the nameservers match a provider we know, the window names it. With locale: "pt-BR", POST /checkdomain and POST /connect also return instructions: the steps in that provider's own panel, in Portuguese, for a single CNAME.
Adding a CNAME by hand at Cloudflare. It has to be set to "DNS only". With the proxy on, the CNAME is not visible in DNS and the verification cannot complete.
To always show the guided steps, even for a provider with automatic setup, open the window with forceManualSetup: true and a prefilledDomain.
Existing records are never deleted
Cnamio adds records, and the only existing one it can change is an SPF policy (extended, every term kept). Before writing it reads what exists and applies the same rules for every provider:
- A CNAME needs a free name: it is not created next to any other record with that name.
- A, AAAA and MX records are never added next to different existing values.
- TXT and CAA values are added next to existing ones, except a second DMARC policy or a second DKIM key at the same selector.
- A domain can publish only one SPF policy, so a requested one is merged into the existing policy: every existing term stays as it is and only the missing mechanisms are added before
all. The user gets the full merged value to paste; where the merge is enabled for the provider, Cnamio edits that one record. It is refused when the result would pass 10 DNS lookups. - Names covered by a wildcard, delegated to another server, proxied or aliased by the provider are left for a person to review.
When something is in the way the API answers 409 with the list of conflicts and nothing is written. In the window, the user sees what already exists and can use another address or adjust that record at the provider.
What your code sees
POST /checkdomain tells you the provider and the path before you start. connectMethods contains api_token when the records can be created with the user's credential:
{
"domain": "shop.customer.com",
"zone": "customer.com",
"provider": "route53",
"setupType": "Automatic",
"connectMethods": ["api_token"],
"nameservers": ["…"]
}
The same provider and the setup_type come back in the connection status and in the webhook, so you can show your user where their DNS is and how the domain was connected. Details in the REST reference.
Need another provider to be automatic?
Guided setup already works with it today. If many of your users keep their DNS at one provider, tell us which at contato@cnamio.com: that is how we choose what to test next.