A custom domain gives your Coderblock app a recognizable production address, so you do not have to use the Coderblock URL automatically assigned to the project.

You can:

• connect a domain you already own by configuring its DNS records through the guided setup;
• buy a new domain directly through Coderblock and let the platform manage DNS and SSL.

This tutorial covers both options and explains how to verify that everything works correctly after publishing.

Before connecting a domain

Before configuring your domain, make sure your app is ready to publish.

Open the live development preview at <app>.coderblock.dev and test the app's main user flows, including:

• navigation and layout on mobile devices;
• sign-up and sign-in, if your app uses accounts;
• forms and database-powered features;
• Stripe checkout, if you have enabled payments;
• the admin area and any other protected sections.

If you find anything that needs fixing, simply describe it to the Coderblock agent in natural language. For example:

Make the navigation responsive and ensure the sign-up form displays clear validation errors.

The app will be updated in the live preview within seconds. A custom domain does not replace the development URL. It simply adds a new address for the published production version of your app.

At this point, choose which setup you want to use:

1. Connect a domain you already own: you will need to update its DNS records through the registrar or DNS provider that manages the domain.
2. Buy a domain through Coderblock: you will complete checkout directly on the platform, and Coderblock will automatically configure DNS and SSL.

---

Option A: Connect a domain you already own

This is the right option if you have already purchased a domain from another provider and can edit its DNS settings.

Step 1: Open the domain settings

Open your Coderblock project and go to Settings → Domains. Select the option to connect an existing domain. Enter the domain you want to use for your app and carefully check that it is spelled correctly before continuing.

---

Step 2: Review the DNS records

Coderblock will display the DNS records required to connect the domain to your project. Keep this page open. You will need it to copy the specified names, types, and values into your DNS provider's control panel. Use the exact records shown for your project. Do not replace them with values from other tutorials or configurations for different services. The destination depends on the specific app you are connecting.

---

Step 3: Open your DNS provider's control panel

Open a new browser tab and sign in to the service that manages your domain's DNS. This may be the registrar where you purchased the domain or a separate DNS provider. Find the section used to manage DNS. Depending on the service, it may be called:

• DNS
• DNS Records
• Zone Editor
• Manage DNS

---

Step 4: Add the records provided by Coderblock

Create or update the DNS records so that they match the values shown in Coderblock. Copy each field carefully and save your changes. Before deleting an existing record, always check what it is used for. A domain may have other records for email or services unrelated to the web app. Only change records that conflict with the address you want to connect, and leave unrelated records unchanged. If your provider automatically appends the domain name to the host field, follow its formatting instructions. The goal is for the saved record to represent the same host and destination specified by Coderblock.

---

Step 5: Return to Coderblock

Return to Settings → Domains and continue the connection process. Keep in mind that DNS updates may not become visible everywhere at the same time. As a result, the domain may not be available immediately after you save the records. If validation fails, compare every field against the values shown by Coderblock again. Pay particular attention to:

• typos;
• duplicate records;
• old records pointing the same host to a different destination.

Publish and test the app in production

Once the domain is connected, click Publish to deploy the production version. Coderblock will publish the app at <app>.coderblock.app or on the connected custom domain, with SSL included.

Open the custom domain in a new tab and verify that:

• the page loads over https://;
• the browser displays the correct domain;
• navigation links stay on the production address;
• authentication and protected pages work;
• forms correctly read and write data in the Postgres database;
• payments use the intended Stripe mode;
• images and files load correctly from storage.

If the app is public-facing, test it on both desktop and mobile devices. Your work does not end once the domain is connected. You can continue editing the app through chat, review updates in the live preview, and publish again whenever you are ready to move them to production.

Option B: Buy a domain directly through Coderblock

If you do not yet own a suitable domain, you can buy one directly through the platform. Open Settings → Domains and select the option to purchase a new domain. Choose the domain you want and complete checkout within Coderblock.

In this case, DNS and SSL are configured automatically, so you will not need to copy records or manually edit an external service's DNS control panel. Once the purchase and setup are complete, publish the app and run the same checks described in the previous section.

In particular, verify:

• the HTTPS address;
• sign-in and sign-up;
• forms;
• files and images;
• any payment flows.

If the domain does not load

If the connected domain does not work as expected, start with this checklist:

1. Check the domain. Make sure the domain entered in Coderblock exactly matches the one whose DNS records you updated.
2. Double-check the DNS records. Even one incorrect character can prevent the domain from connecting properly.
3. Look for conflicts. An old record may still point the same host to another service.
4. Wait for the DNS update. Changes can take time to propagate.
5. Make sure you published the app. The development preview and production version are separate environments.
6. Try the full HTTPS address. Enter the URL directly with https://.
7. Try a private browsing window. This helps rule out issues caused by cached data, redirects, or older versions stored by the browser.

One important note: do not repeatedly change DNS records while the configuration is updating. If the values match those provided by Coderblock, unnecessary changes can make the process more difficult.

Final checklist

The domain is configured correctly when:

• the domain appears under Settings → Domains in the project;
• the DNS records match the configuration provided by Coderblock, or they were configured automatically after a purchase through the platform;
• the app has been published;
• the custom domain opens over HTTPS;
• the app's main user flows work correctly in production.

Your domain is ready

Your Coderblock app now has a custom production address that you can share with customers, users, and stakeholders. From here, you can continue developing it as usual: chat → edit → preview → publish, while keeping the custom domain as the entry point to the live version.