How to Manage your DNS Settings for Hypernode

Hypernode is a cloud-based hosting service. In case of an up- or downgrade, your shop can transparently be moved to other hardware with different specs. When upgrading or downgrading a Hypernode plan, we create a second node, migrate your shop to this new node, and then remove the old one.

Thanks to Hypernode’s very cool Dedicated IPfeature, the IP address of your Hypernode does not (!) change when you change a Hypernode plan. However, there are three exceptions to take into account.

This article explains two ways to handle your DNS. Please decide for yourself the best option for your specific situation.

Dedicated IP on Hypernode – 3 exceptions

There are three exceptions in which you cannot benefit from a dedicated IP and which may have an impact on how you would like to manage your DNS:

  1. A change of cloud provider – also when switching between Falcon and Eagle plans – will trigger an IP change

  2. The IP address will also change if you request your node to be booted in a different region (data center).

  3. In extreme emergency situations (like fire or longtime power outages), we might need to migrate your Hypernode to another data center. Luckily these chances are very low.

If you’re likely to switch between Falcon and Eagle plans in the future, we recommend you move your domain(s) to Hypernode so we can handle the DNS of your domains to avoid downtime. Or, use the DNS settings as explained below (by using CNAME and not A record).

Two ways to handle your DNS

There are two ways to handle your DNS. Option 1 is available if your domain is registered with (or moved to) Hypernode.

  1. Move your domain(s) to Hypernode and let Hypernode manage the DNS

  2. Manage an external DNS by pointing your domain(s) to Hypernode by using CNAME and not A record

Good to know:

Options 1 and 2 will prevent DNS downtime.

If you cannot benefit from a dedicated IP on Hypernode, please decide the best way to handle your DNS. We recommend always moving your domains to Hypernode. We’ve included a detailed explanation of options 1 and 2 below.

Option 1: let us manage your DNS

What happens at the background?

We will create an A record for example.com and a CNAME record for www.example.com. Other A- and CNAME records for example.com and www.example.com will be removed. Records for subdomains are not touched, so it’s still possible (and perfectly reasonable) to have a subdomain for your blog on blog.example.com. If a domain is linked to a Hypernode, it’s no longer possible to manually change the apex records that point to your Hypernode.

Please note:

  • By letting us manage your DNS, you will also be able to use your apex domain

  • Preferably the TTL for the DNS records is low to make the transition to Hypernode quick. Please check this before making any changes to your DNS.

Option 2: Manage an external DNS by pointing your domain to Hypernode by using CNAME and not an A-record

If you cannot transfer your DNS to Hypernode, you can choose to only point the CNAME record to your Hypernode. We do not recommend this option because you cannot use SSL on your naked (also called apex) domain name: example.com, without the ‘www.’-prefix.

If this is not an issue, the configuration needed can be found below:

Configuration:

  • Have a CNAME for your www-domain + an A Record that directs to the dedicated IP address of your Hypernode

These examples assume you have a site called example.com and a Hypernode called example.hypernode.io.

The recommended way to configure your DNS is to create a CNAME record in your DNS configuration, pointing to Hypernode:

www.example.com      CNAME       example.hypernode.io

This means that www.example.com will point to wherever example.hypernode.io points, and we will make sure that that always points to the correct IP address.

Please note: You can also configure your wildcard (*) domain name to Hypernode.

*.example.com      CNAME       example.hypernode.io

DNS and Hypernode Managed Vhosts

With Hypernode Managed Vhosts (HMV), you must add a new vhost for every domain you want to link to your Hypernode. So you need to configure your DNS correctly and add a new vhost for the domain.

To add a new vhost, for example the domain name www.example.com, to your configuration, you can run the command hypernode-manage-vhosts www.example.com. This will create a new vhost configuration in /data/web/nginx/www.example.com/, using the Magento 2 template.

Please note that defining the vhosts ‘www.example.com’, does not automatically add ‘example.com’ as a vhost. You will have to manually define a vhost for this. Since most people want their ‘example.com’ to redirect to ‘www.example.com’, you can use the --type wwwizer argument to set this up. This will configure the vhost to redirect all traffic to the www-version of the domain.

Read more about Hypernode Managed Vhosts in this article.

Redirects in Nginx

If you want to force a redirect to www. or the non-www. domain, you can use a redirect.

You can read how this works in this article.

Shop on a subdomain?

If you host your shop on a subdomain (for example, shop.example.com), and you don’t want to be available on www.shop.example.com, simply create a CNAME-record pointing to your Hypernode, and it will work:

shop.example.com      CNAME       example.hypernode.io