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 first create a second node, migrate your shop to this new node and then remove the old one.

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

This article explains 3 ways to handle your DNS. Please decide for yourself what would be the best option for your specific situation.

Dedicated IP on Hypernode – 3 exceptions

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

  1. A change of cloud provider – also when switching between Professional and Excellence plans – will trigger an IP-change
  2. If you request your node to be booted in a different region (data centre) the IP-address will change as well.
  3. In extreme emergency situations (like fire or longtime power outages) we might need to migrate your Hypernode to another data centre. Luckily these chances are very low.

If you likely will switch between Professional and Excellence plans in the future, we recommend you to move your domain(s) to Byte 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).

Three ways to handle your DNS

There are 3 ways to handle your DNS. Only Dutch customers who have access to a Service Panel can choose option 1.

  1. Move your domain(s) to Byte and let Byte manage the DNS (Dutch customers only)
  2. Manage an external DNS by pointing your domain(s) to Hypernode by using CNAME and not A record
  3. Manage an external DNS by pointing your domain(s) to the IP-address of Hypernode via A record

Good to know:

Option 1 and 2 will prevent DNS downtime.

Option 2 has an important disadvantage: your cannot use SSL in combination with your naked domain. People that directly visit https://yourdomain.com/, will get a certificate warning from the browser.

Option 3 is the best option in case of an external DNS and you want to make use of https://yourdomain.com/, but you will encounter DNS downtime if the IP-address of your Hypernode changes.

As there are situations you cannot benefit from a dedicated IP on Hypernode, please decide for yourself what is the best way to handle DNS. Our recommendation is always to move your domains to Byte if possible.

Below you will find a detailed explanation of option 1 and 2.

Dutch customers only: let us manage your DNS

If you have your domain at Byte, we can manage your DNS. We will update the DNS records when the IP of your Hypernode changes. The steps:

  1. Log in to your Service Panel with your customer number and password and select your Hypernode.
  2. Navigate to ‘SSL & DNS instellingen’ under tab ‘Instellingen’. Here, you will see an overview of all available domains.
  3. Search for the domain you would like to link to your Hypernode
  4. Go to the column ‘DNS Beheren’, click on “Beschikbaar” and select ‘Koppel domeinnaam aan deze Hypernode’.

Whenever you want to unlink a domain, simply choose ‘Ontkoppel domeinnaam van deze Hypernode’.

When linking a domain to your Hypernode, we will immediately change the DNS records of the domain. Plan this moment carefully when migrating to Hypernode, and make sure content on the original location is no longer used.

What happens at the background?

We will create an A-record for domain.com and a CNAME-record for www.domain.com. Other A- and CNAME-records for both domain.com and www.domain.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.domain.com, which points to plan on the Byte cluster platform.

If a domain is linked to a Hypernode, it’s no longer possible to manually change the apex records that points to your Hypernode. We will make a backup of the record we adjust. These show up in the DNS admin as TXT records for __backup__.domain.com. If you unlink your Hypernode, we will put the backup records back in place. You can delete or change them if you choose to do so.

Keep in mind:

  • By letting us manage your DNS, you will also be able to use your apex domain
  • Preferably the TTL for the DNS records is reasonably low to make the transition to Hypernode quick. Check this beforehand.

Manage your own DNS: use CNAME, not A


  • Have a CNAME for your www-domain + an ANAME/ALIAS pseudo-record for your apex (also called naked) domain. This requires a DNS provider that supports those types of records.
  • Have a CNAME for your www-domain + an A record for your apex (also called naked) domain pointing to a redirector that redirects to the www-domain.

These examples assume you have a site called yourdomain.com and a Hypernode called yourd01.hypernode.io.
The recommended way to configure your DNS is to create a CNAME record in your DNS configuration, pointing to Hypernode:

This means that www.yourdomain.com will point to wherever yourd01.hypernode.io points, and we will make sure that that always points to the correct IP address.
NB: You can also configure your wildcard (*) domain name to Hypernode.

‘Apex’ or ‘naked’ domain names when managing your own DNS

Problems arise when people visit your naked (also called apex) domain name: yourdomain.com, without the ‘www.’-prefix. It is not possible to create a CNAME record for your apex domain.

Some DNS providers, like DNSimple or DNS Made Easy have the possibility to create ALIAS or ANAME pseudo-records. These behave like CNAME-records for apex domains. Unfortunately they are not wide-spread yet, so the chances are your provider doesn’t support it.

Another solution is to redirect traffic for the apex domain yourdomain.com to its www-counterpart www.yourdomain.com. You might be able to configure redirecting with your DNS provider, or you can use our free wwwizer service. Just configure the following A-records for your apex domain and they will redirect all traffic for you.

NB: Note that if you make use of the www-izer redirect servers, people that visit https://yourdomain.com directly will get an error message, either indicating that there is no https available or a plain connection refused error.

Don’t fancy these solutions? Migrate your domain to Byte and let us manage your DNS.

Redirects in Nginx

If you want to force a redirect to either the www. or the non-www. domein, 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.yourdomain.com), and you don’t want to be available on www.shop.yourdomain.com, you can forget all about the wwwizer service, and there’s no need to add the two IP-addresses in your A-records as explained above. Simply create a CNAME-record pointing to your Hypernode, and it will work:

Use the Store Front Status check in Magereport Premium

If you visit Magereport Premium with your Hypernode plan, you can verify whether your domains are redirected to your Hypernode.

It will tell you if they’re live (DNS is redirected to Hypernode) and if it’s configured correctly. In case, the storefront tool tells you that the DNS is misconfigured it will present an example of how you should configure the DNS correctly.