Updating DNS Records

In this article

  1. General Information
  2. Add CNAME
  3. Add A-records
  4. Adding a subdomain
  5. About AAAA-records

It is recommended to already apply several changes to the DNS records of your domain.

Changes that have been made to DNS Records are known to take some time to update globally.


Each domain comes with a set of DNS Records, when connecting your domain to your project we have to edit our A-record & CNAME.

👉 Head to the control panel of your domain name hosting provider (e.g. Combell, one.com, GoDaddy, ...) to access the DNS records of your domain name.

A domain name can only be added when a project is live

1. CNAME-record

A CNAME record can map the web address www.example.com to the actual website for the domain example.com.

Add this CNAME record to your DNS settings

refer www.yourdomain.com to destination dns.sitemn.gr


Example:

Screenshot_64-2

Test your CNAME:


2. A-record

An A-record links a domain to an IP address. This way, your domain name refers to your hosting account on servers.


Add these 2 A-records to your DNS settings

refer *.yourdomain.com to IP address 185.86.17.50 

refer yourdomain.com to IP address 185.86.17.50

Test your A-Record:

3. Some Tips

PRO TIP

Set your TTL as low as possible.

Lower values mean your DNS gets updated more quickly — which means if you make changes to where your website is hosted, they take effect more quickly.

Keep in mind, it can take some time before any DNS changes take effect. For an A-record or CNAME it could easily take up to 24 hours.

Always be careful when deleting already existing records, if you're not 100% sure contact your hosting support.

4. Adding a subdomain

To add a subdomain, there are a few additional steps involved. First, you need to add a new CNAME record and an A-record.

Both the A-record & CNAME have to point to 185.86.17.50 & use a TTL of 60


For example, when adding the subdomain, "connect," to our domain: mijnwebsite.be,

Additionally, we need add the CNAME record, such as www.connect

About AAAA-Records

When a user visits your domain, their device first tries to connect via IPv6 (using the AAAA-record if available). If the AAAA-record points to a different location than the A-record, this can cause conflicts or errors, as traffic may be routed to the wrong server.

Our platform operates based on the location specified in the A-record. If the AAAA-record points to another server, the connection may not work properly, especially for IPv6 users.

Ensure the AAAA-record either matches the A-record or is not set at all to avoid potential issues.