Besides the free version of CDN service, Rapid.Space also provide a premium-level CDN frontend service (Rapid.CDN) for professional needs.
In order to configure domain www.example.com to be used with Rapid.CDN the DNS entry has to be set as:
www.example.com IN CNAME world.geoip.nxdcdn.com
This works for all subdomains, like app.example.com, and also for wildcards like *.example.com.
SLA: Rapid.CDN provides full support and monitors the Rapid.CDN nodes to assure that such configuration is always working.
Rapid.Space advises to setup the reply while accessing:
To be redirection to:
Thanks to this all features of Rapid.CDN will be used.
But the top-level domain has to live somewhere, and of course can be served by Rapid.CDN.
The current DNS configuration is:
example.com IN A 18.104.22.168
example.com IN A 22.214.171.124
The TTL value has been omitted, as it shall follow typical DNS configuration of the provider.
SLA: For this configuration Rapid.CDN provides only best effort support, as there are some critical cases, which can lead to this IP being unavailable, due to machine or datacenter failure.
Note: Despite that those IPs are located in well supported datacenters, it can change any time. In such case Rapid.Space will update this how-to and also publish status.rapid.space update.
Rapid.CDN does not provide a solution for geographically smart and zone failover IP (like for example it would be used with AnyCast supported service provider).
If customer requires such solution for it's top-level domain example.com one can use other hosting provider to setup proposed redirection to https://www.example.com/
Choosing proper hosting provider will allow to have always working IP for top-level domain, which will lead to high SLA for top-level domain.