Creating a CNAME record for your P2P instance

As explained in this Article, your P2P platform will be given a unique identifier, which will be used to log into the backend. You will be given the option to choose the identifier during the on-boarding process.

Behind the scenes, this identifier is also used to point to the server instance which is running your P2P platform. In practice, the identifier will be added as as subdomain for `raisenow.net`, like for example: `myidentifier.raisenow.net`.

In order for your platform to be reachable via a custom domain of your choosing, a DNS record needs to be created that points to this subdomain. You might have to coordinate this with your IT vendor.

wefund.example.com.   3600   IN   CNAME   myidentifier.raisenow.net.

Why a CNAME record

We cannot guarantee that the IP addresses we are using will stay the same over time, it is therefore more safe to handle this via canonical name that is managed on our side, should there ever be changes.

Setting the TTL

Since the identifier itself is not at all likely to change, you can set the TTL (Time to live) to at least one hour (3600), though once your platform is live, we recommend setting it to as high as a whole day (86400).

Using multiple URLs / Domain names or a dedicated second level domain

While you can only use one distinct domain name to publish the platform, it is possible to point multiple domain names to the subdomain representing your identifier. They can then be individually redirected to for example different language versions of your platform.

It's also possible to use a dedicated second level domain for your platform, without a subdomain, but in this case you will need to create an A record pointing to an IP address.

Please contact our Professional Services Team for more information.