Currently domain forwarding comes with the next limitations:
Creation of the forwarding is not realtime. Please wait up to 24 hours before everything is set up correctly (the DNS change, the forwarding itself and the billing).
There is no API call yet to activate this service
Already created forwarders can be updated or deleted through the control panel, but please keep in mind that these changes are not realtime.
Domain forwarding can be enabled in the second step of domain registration wizard by clicking on "Domain forwarding" checkbox.
In order to configure it, you need to click "click to configure" and navigate down to "domain forwarding" section.
Choose forwarding type and enter the destination URL.
Be sure to add http:// or https:// to the URL!
Forwarding type: permanent (301) vs temporary (302)
A 301 redirect means that the page has permanently moved to a new location.
A 302 redirect means that the move is only temporary. Search engines need to figure out whether to keep the old page, or replace it with the one found at the new location. More information is available online.
If you use the Openprovider nameservers, we will set up the A-record for you. In case you use your own nameservers, please ensure that the A-record for this domain in your DNS zone points to IP address 18.104.22.168.
If you also want to redirect sub domains under this domain name, you can do so by creating CNAME records in your DNS zone.
Now the setup for domain forwarding is complete.
If forwarding is not working in 24 hours, please run through the checklist below to make sure configuration is finalized:
- Make sure the A-record in DNS zone of the domain is set to 22.214.171.124
- Make sure (e.g. via the dig command line tool) that the A-record change is already replicated through DNS hierarchy (can take up to 24 hours depends on your TTL settings on the DNS zone record)
- If the above checks are successful - enter the domain name in your browser and confirm that it forwards to the right destination! In case of browser caching, it is more safe to check via any public service that can show HTTP headers, e.g. helloacm.com.
Forwarding from a domain that has active SSL certificate (e.g https://domainname.com) will not work until SSL certificate on destination domain covers source domain as well.