---
title: "Custom Domain Names"
canonical: "https://red-ant-documentation.refined.site/space/RDD/618496031/Custom%20Domain%20Names"
format: markdown
---
RetailOS allows you to use your own custom domain name for the web client. This guide explains how to get set up.

> Macro (toc)

## Setup

Should you wish to have your custom domain name on the app (for example on a public-facing page) Red ant can configure our platform to use your specified domain name. Once you have provided this to us we can generate a DNS target and send this over to your team. It will look something like this: `theoretical-example-aa9999tttuuuuu9ee33oo54.herokudns.com`. You will then need to have your DNS provider point towards the target we send over in order to authorise us to be able to use the domain.

## Root domains

For root domains like [example.com](http://example.com) you would need an `ALIAS`, `ANAME` or `FLATTENING` record for the root domain that points to the DNS Target.

Whichever provider you have, point the ALIAS/ANAME/CNAME entry for your root domain to the DNS Target, just as you would with a CNAME record:

Depending on the DNS provider, an empty or `@` Name value identifies the root domain.

| Record | Name | Target |
| --- | --- | --- |
| `ALIAS` or `ANAME` | <empty> or `@` | `hidden-sierra-7936.herokudns.com.` |

## Subdomains

For subdomains like [test.example.com](http://test.example.com) you would need a `CNAME` record that points to the DNS Target.

The following table shows common `CNAME` record patterns:

| Record | Name | Target |
| --- | --- | --- |
| `CNAME` | `www` | `whispering-willow-5678.herokudns.com.` |
| `CNAME` | `othersubdomain` | `autumn-sunset-1495.herokudns.com.` |
| `CNAME` | `examplesecure` | `example-12345.ssl.herokudns.com.` |

## Authorisation/Confirmation

Make sure that there are **no conflicting records** set for the same host. Once you have done this there might be a delay while DNS changes propagate but we will confirm wether the app is accessible via that domain.