Skip to main content

​
Idea

There are several reasons why it can be useful to use a custom domain (e.g. https://licensing.your-domain.com) instead of calling Devolens Web API directly. A common reason is if your clients require that the IP must originate from a specific geographical location, for example, if you sell software to government buyers or other companies with strict firewalls.

​
Getting started

Depending on the reason why a custom domain is needed, there are several approaches we can recommend.

​
Approach 1: solving geo restrictions

If you have customers who are behind a firewall (e.g. a US customer that does not allow requests to be sent outside of US), you can either use our endpoint that is proxied through Cloudflare or add an A record in your DNS that is proxied through Cloudflare.

​
Using our own endpoint

The endpoint above is proxied through Cloudflare. In tests by us and our customers, it has resolved to an IP address classified as US-based when called from the US, and to a European IP address when called from Europe. Results may vary by network and location, so we recommend testing from the affected customer’s network. If a specific IP address or location is required, consider the reverse-proxy approach described below.

​
Using your own domain

If you are using Cloudflare, you can add an A record that points to 20.82.170.150. The record should be proxied (i.e. yellow icon in Cloudflare).

​
Approach 2: setting a specific IP

If you need to ensure that requests are sent to a specific IP adress that you control, you can use a reverse proxy instead. One way to accomplish this is by creating a VM that runs nginx, as described in this article. This would require more maintenance, and we do not recommend it as a first option.