Custom domains

Every HTTP project created on Zenifra automatically receives a free platform subdomain. This address lets you access the application without buying or configuring your own domain.

The default format is:

project-name.clients.zenifra.com

You can use this subdomain for testing, initial validation, internal environments, or as an operational fallback. For production, you can also connect your own domain, such as:

mysite.com.br
www.mysite.com.br
app.mysite.com.br

How domain connection works

To connect your own domain to an application hosted on Zenifra, follow this general flow:

Create the project on Zenifra.
Enter the desired domain in the Zenifra panel.
Configure the DNS records at the provider where the domain is hosted.
Wait for DNS validation and SSL certificate issuance.

Important: The DNS target that must be used becomes available in the Zenifra panel after the project is created. For HTTP projects, this target is usually an address such as project-name.clients.zenifra.com.

Do not use IPs found in examples, old screenshots, or support replies outside the context of your project. The correct value is always the one shown in the Zenifra panel for that specific domain and project. For custom domains on Zenifra, the records customers need to configure are CNAME records for routing and TXT records for SSL validation.

After DNS points correctly, Zenifra validates the domain and automatically configures internal routing to send traffic to the correct application. Zenifra also handles HTTPS/SSL configuration for the custom domain after DNS validation.

Apex domain and subdomain

Before creating DNS records, identify whether you want to point the apex domain or a subdomain.

Apex domain

The apex domain is the main address registered with the domain provider:

yourdomain.com.br

It can also appear as a root domain or naked domain in some DNS providers.

Subdomain

Subdomains are names created below the apex domain:

www.yourdomain.com.br
app.yourdomain.com.br
system.yourdomain.com.br

Use subdomains when you want to separate applications, environments, or product areas, such as a public website, admin panel, and API.

DNS record types

Use the records shown in the Zenifra panel. The table below summarizes the most common cases.

Case	Type	Name, Host, or Name field	Value
Apex domain at a provider with flattening	CNAME with flattening	`@`	`CNAME address shown in the Zenifra panel`
`www` subdomain	CNAME	`www`	`CNAME address shown in the Zenifra panel`
`app` subdomain	CNAME	`app`	`CNAME address shown in the Zenifra panel`

In some DNS providers, the field can be called Nome, Host, or Name. These fields usually accept:

@ for the apex domain, such as yourdomain.com.br
www for www.yourdomain.com.br
app for app.yourdomain.com.br

Configure an apex domain

A regular CNAME usually cannot be used directly on the apex domain, such as yourdomain.com.br. This is a common DNS rule and appears in providers such as Registro.br, where the root (@) does not accept a CNAME.

To use the apex domain with Zenifra, choose one of the options below.

Recommended option: provider with CNAME flattening

Use a DNS provider that supports CNAME flattening, such as Cloudflare or another provider with an equivalent feature. In this case, configure a CNAME on the apex domain pointing to the target shown in the Zenifra panel.

Type: CNAME
Name: @
Value: CNAME address shown in the Zenifra panel

On Cloudflare, for example, you can create a CNAME at the root (@) and Cloudflare automatically flattens it into DNS-compatible responses.

When the provider does not support CNAME at the root

If the current provider does not allow CNAME at the root and does not offer CNAME flattening, there are two practical options:

move the DNS zone to a provider that supports flattening, such as Cloudflare
keep the apex domain outside Zenifra and redirect yourdomain.com.br to www.yourdomain.com.br using an external service that supports HTTPS on the apex

Registro.br can remain the domain registrar even when the authoritative nameservers are moved to another DNS provider.

Do not point the root to IPs copied from the Zenifra CNAME, Cloudflare DNS answers, or old examples. That kind of configuration may work by accident at a specific moment, but it is fragile and can break without notice.

Configure subdomains

For subdomains, such as www, app, or system, create a CNAME record pointing to the address shown in the Zenifra panel.

Example for www.yourdomain.com.br:

Type: CNAME
Name: www
Value: CNAME address shown in the Zenifra panel

Example for app.yourdomain.com.br:

Type: CNAME
Name: app
Value: CNAME address shown in the Zenifra panel

Do not create conflicting records for the same name. For example, www should have only the CNAME indicated by Zenifra, plus the TXT validation records when requested.

DNS configuration example

Suppose you want to configure the apex domain and www for your own domain on Zenifra. After creating the project and entering the domains in the panel, create records like these at your DNS provider.

For the apex domain, when the provider supports flattening:

Type: CNAME
Name: @
Value: CNAME address shown in the Zenifra panel

For www:

Type: CNAME
Name: www
Value: CNAME address shown in the Zenifra panel

After saving the records, return to the Zenifra panel and wait for validation. Propagation can take a few minutes or up to a few hours, depending on the DNS provider.

Validation, routing, and HTTPS

When DNS records propagate, Zenifra checks whether the domain points to the expected destination. After validation, the platform configures internal routing so requests to the custom domain reach the correct application.

HTTPS is also configured by Zenifra. SSL certificate issuance depends on DNS pointing correctly and may require TXT validation records.

SSL validation TXT records

During certificate issuance, the Zenifra panel may show one or more TXT records with a name similar to this:

Type: TXT
Name: _acme-challenge.www.yourdomain.com.br
Value: validation token shown in the Zenifra panel

If the panel shows two TXT records with the same name, publish both values. This is normal for ACME/TLS validation. Do not replace one token with the other.

Type: TXT
Name: _acme-challenge.www.yourdomain.com.br
Value: first-token

Type: TXT
Name: _acme-challenge.www.yourdomain.com.br
Value: second-token

While the certificate is being validated, the domain may already appear as registered, but HTTPS can still fail. Wait until the SSL status is active before considering the setup complete. If the certificate has not been issued yet, check whether all TXT records were saved correctly and wait for propagation before opening a support request.

Best practices

Use the apex domain and www whenever possible, especially for public applications.
Avoid changing DNS records without understanding the impact on email, website, APIs, and other services.
Check that there are no conflicting records for the same name; keep only the CNAME indicated by Zenifra and the required validation TXT records.
For apex domains, prefer a DNS provider with CNAME flattening.
Publish all TXT validation records shown in the panel; multiple TXT records with the same name may be required.
Wait for DNS propagation before opening a support request.
Keep the domain active and renewed at the registrar.
Keep the free Zenifra subdomain as an operational reference during the initial setup.

Next steps

FAQ

Can I use my own domain on Zenifra?

Yes. In addition to the free Zenifra subdomain, you can connect your own domain to the project, such as mysite.com.br, www.mysite.com.br, or app.mysite.com.br, depending on the features available in your plan.

Where do I find the DNS target?

The DNS target appears in the Zenifra panel after the project has been created and the domain has been entered. For HTTP projects, this target is usually an address under the clients.zenifra.com zone. Always use the value shown in the panel for the corresponding project.

Can I use CNAME on the apex domain?

Usually, not as a regular CNAME. To point the apex domain to Zenifra, use a DNS provider with CNAME flattening, where the configured record is still a CNAME, or redirect the apex domain to www through an external service that supports HTTPS.

Does Registro.br allow CNAME on the apex domain?

Not in the regular DNS model. If the domain uses Registro.br authoritative DNS and you need to point yourdomain.com.br to Zenifra, use a DNS provider with CNAME flattening, or configure an HTTPS redirect from the apex to www.

How long does DNS propagation take?

DNS can take a few minutes or up to a few hours to propagate, depending on the DNS provider, the configured TTL, and the network used to access the domain.

Does Zenifra configure HTTPS automatically?

Yes. After DNS points correctly and the domain is validated, Zenifra automatically configures HTTPS/SSL for the custom domain.

Why does HTTPS still fail if the CNAME is already correct?

Because certificate issuance may also depend on TXT records under _acme-challenge. If there are two TXT tokens for the same name, publish both. After the records propagate, the certificate authority may still take a few minutes to issue and activate the certificate.

Do I need to use Cloudflare?

No. You do not have to use Cloudflare. You can keep the domain at your current DNS provider as long as you can create the required DNS records. For apex domains, the provider must support CNAME flattening if you want to point the root directly to Zenifra.

Can I use www and the apex domain at the same time?

Yes. You can configure yourdomain.com.br and www.yourdomain.com.br for the same project, as long as both are added in the Zenifra panel and have the correct DNS records.

On this page