Configure Bocadium DNS by provider in Uruguay

Before you start: registrar and DNS provider may differ

The place where you bought or renew the domain is not necessarily the service publishing its DNS zone. Check the nameservers (NS): if they point to Cloudflare, a hosting provider or another service, create the Bocadium records there.

• Do not change nameservers only to connect Bocadium if the current DNS zone already works.
• Do not remove MX, SPF, DKIM or DMARC records if you use email on the domain.
• In Custom domain, Bocadium always shows the authoritative values: A for @, CNAME for www and TXT _bocadium-verify.

NIC.UY / SeCIU

1. 1

   Sign in to NIC.UY with the account that manages the domain and open the domain you want to connect.

2. 2

   Review the configured nameservers to identify where the DNS zone is actually managed.

3. 3

   If the zone is managed by the DNS service associated with the domain, add the A, CNAME and TXT records shown by Bocadium there. If it is delegated, make the change at the provider indicated by the NS records.

4. 4

   Save the changes and return to Bocadium to verify.

ANTEL / Dominios UY

1. 1

   Sign in to Dominios UY and open “My domains”.

2. 2

   Check whether the domain is hosted on Dominios UY DNS or delegated to external nameservers.

3. 3

   If hosted there, add the records shown by Bocadium in DNS management. If delegated, edit the zone at the external provider.

4. 4

   Return to Bocadium and press “Verify” once the records have started propagating.

NetGate

1. 1

   Confirm that the domain nameservers correspond to the DNS managed by NetGate.

2. 2

   Copy the three A, CNAME and TXT records from Bocadium without changing their values.

3. 3

   If your service includes a DNS editor, add them there. If the zone is managed through support, send support the exact type, name and value for each record.

4. 4

   Verify the domain from Bocadium without changing existing email records.

HostingenlaWeb / RegistraTu.UY

1. 1

   Sign in to the panel where you manage the domain and review its nameservers.

2. 2

   If DNS management is hosted there, open the zone and add A, CNAME and TXT using the Bocadium values.

3. 3

   If the domain is delegated, make the changes at the provider pointed to by the NS records instead of changing delegation.

4. 4

   Wait for propagation and verify from Bocadium.

Montevideo COMM

1. 1

   Check the nameservers to confirm Montevideo COMM is the authoritative DNS provider.

2. 2

   If you have access to DNS zone management, add the three records shown by Bocadium.

3. 3

   If your service does not expose a zone editor, ask support to publish those records without changing MX, SPF, DKIM or DMARC.

4. 4

   Verify the domain in Bocadium once the changes are publicly visible.

Intersys Uruguay

1. 1

   Review the nameservers to confirm where the DNS zone is hosted.

2. 2

   If your Intersys service manages DNS through a panel or cPanel, open the zone editor.

3. 3

   Create A for @, CNAME for www and TXT _bocadium-verify exactly as shown in Bocadium.

4. 4

   If the NS records point to a third party, make the change there.

Netuy

1. 1

   Sign in to Netuy and open the DNS service for the domain.

2. 2

   In Self-managed DNS, add the A record for @, the CNAME for www and the TXT _bocadium-verify shown by Bocadium.

3. 3

   Keep email records and any other service already using the domain.

4. 4

   Save, wait for propagation and verify from Bocadium.

Hosting Montevideo

1. 1

   Sign in to the customer area and verify where the domain DNS zone is managed.

2. 2

   If DNS is managed from its panel or hosting service, open the zone editor and add A, CNAME and TXT.

3. 3

   If the nameservers point to another provider, edit the zone at that provider.

4. 4

   Return to Bocadium and verify.

If DNS is delegated to Cloudflare

1. 1

   Open Cloudflare → DNS → Records and create the three records shown by Bocadium.

2. 2

   During initial verification leave A and CNAME as “DNS only” (gray cloud), so Bocadium can resolve the configured targets directly.

3. 3

   The TXT record is not proxied and must keep the exact token generated for your domain.

4. 4

   Return to Bocadium and press “Verify”.

If Bocadium still does not verify

• Confirm you edited the authoritative DNS zone by checking the current nameservers.
• Check that @ does not have another A or AAAA record still sending traffic to the previous site.
• Check that www does not have another conflicting A or CNAME.
• Copy the full TXT value: each business gets a different token and another domain token cannot be reused.
• If the apex domain still has an AAAA record from a previous host, some clients may keep reaching the old site over IPv6. Remove that AAAA unless Bocadium explicitly gives you an IPv6 target.
• If DNS verifies but HTTPS stays pending, also review CAA: when CAA records exist they must authorize letsencrypt.org so Dokploy can issue the certificate.
• If DNS is correct but HTTPS remains pending, press Verify again. Bocadium rechecks DNS, registers the domain in Dokploy and checks whether TLS is responding.