Remove wwwizer service references from DNS docs

docs/best-practices/testing/how-to-go-live-with-your-hypernode.md

@@ -63,15 +63,11 @@ Note: from now on, database changes (orders) will be written to Hypernode, but n
 
 Remove the maintenance flag on the Hypernode, so customers accessing the new site won’t hit the maintenance page.
 
-## Step 5: Change Your Base URL to Include WWW
-
-Only if you use Hypernode’s WWW-redirection service, ensure that the base URL of your shop starts with [www](http://www). or a subdomain such as shop. Otherwise, your visitors will bounce back and forth between the redirection service and the Hypernode.
-
-## Step 6: Flush Magento Cache on Hypernode
+## Step 5: Flush Magento Cache on Hypernode
 
 Flush the cache of Magento on the Hypernode. (`magerun cache:flush`)
 
-## Step 7: Set up Hypernode Managed Vhosts
+## Step 6: Set up Hypernode Managed Vhosts
 
 Due to this configuration it is required to 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.
 
@@ -81,23 +77,20 @@ Please note that defining the vhosts '[www.example.com](http://www.example.com)'
 
 Read more about Hypernode Managed Vhosts in [this article](../../hypernode-platform/nginx/hypernode-managed-vhosts.md).
 
-## Step 8: Change DNS Records
+## Step 7: Change DNS Records
 
 ### Web Records
 
 See our manual on configuring DNS for more information. As the DNS changes are propagated, traffic will go to your Hypernode.
 
-There are 3 ways to handle your DNS. Option 1 is available if your domain is registered with (or moved to) Hypernode.
+There are 2 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.
 1. Manage an external DNS by pointing your domain(s) to Hypernode by using CNAME and not A record.
-1. 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 Hypernode if possible.
 
@@ -119,19 +112,19 @@ mydomain.com TXT v=spf1 mx:mydomain.com include:spf.appname.hypernode.io ~all
 
 For more information have a look at [our article about SPF records](../../hypernode-platform/dns/how-to-set-up-your-spf-records-for-hypernode.md).
 
-## Step 9: Configure SSL
+## Step 8: Configure SSL
 
 Enable SSL for your shop for safety and to improve search engine optimisation.
 
 You can find a detailed how-to in [this article](../../hypernode-platform/nginx/how-to-configure-your-shop-to-only-use-https.md) about configuring SSL on your shop.
 
-## Step 10: Configure Cron
+## Step 9: Configure Cron
 
 Configure cron jobs to run on your Hypernode (`crontab -e`), and configure them not to run on your old host (`crontab -ir`).
 
 Note that the time on Hypernode is configured to UTC, so the times used in the crontab are one or two hours later than Central European Time. More information about cronjobs can be found in [Configure Cronjobs on Hypernode](../../hypernode-platform/tools/how-to-use-periodic-tasks-cronjobs-on-hypernode.md).
 
-## Step 11: Configure Backups on Hypernode (Optional)
+## Step 10: Configure Backups on Hypernode (Optional)
 
 For Hypernode Falcon S (or up) and Eagle hosting plans free backups are available. If you need a backup, contact us via support@hypernode.com.
 

docs/hypernode-platform/dns/how-to-manage-your-dns-settings-for-hypernode.md

@@ -1,7 +1,7 @@
 ---
 myst:
   html_meta:
-    description: This article explains three ways to handle your DNS. Please decide
+    description: This article explains two ways to handle your DNS. Please decide
       for yourself the best option for your specific situation.
     title: How to manage your DNS settings on a Hypernode?
 redirect_from:
@@ -17,7 +17,7 @@ Hypernode is a cloud-based hosting service. In case of an up- or downgrade, your
 
 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 three exceptions to take into account.
 
-**This article explains three ways to handle your DNS. Please decide for yourself the best option for your specific situation.**
+**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
 
@@ -29,22 +29,17 @@ There are three exceptions in which you cannot benefit from a dedicated IP and w
 
 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).
 
-## Three ways to handle your DNS
+## Two ways to handle your DNS
 
-There are three ways to handle your DNS. Option 1 is available if your domain is registered with (or moved to) Hypernode.
+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
 1. Manage an external DNS by pointing your domain(s) to Hypernode by using CNAME and not A record
-1. Manage an external DNS by pointing your domain(s) to the IP address of Hypernode via A record
 
 Good to know:
 
 *Options 1 and 2 will prevent DNS downtime.*
 
-*Option 2 has a significant disadvantage: you cannot use SSL with your naked domain. People who visit <https://example.com/>, will get a certificate warning from the browser.*
-
-*Option 3 is the best in case of an external DNS, and you want to make use of <https://example.com/>, but you will encounter DNS downtime if the IP address of your Hypernode changes.*
-
 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
@@ -85,7 +80,6 @@ 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
-- 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 (our wwwizers)
 
 These examples assume you have a site called example.com and a Hypernode called example.hypernode.io.
 
@@ -103,30 +97,6 @@ This means that [www.example.com](http://www.example.com) will point to wherever
 *.example.com      CNAME       example.hypernode.io
 ```
 
-## Option 3: Manage an external DNS by pointing your domain(s) to Hypernode by using CNAME and not an A-record
-
-Problems arise when people visit your naked (also called apex) domain name: example.com, without the ‘www.’-prefix. It is not possible to create a CNAME record for your apex domain.
-
-The preferred way to redirect your apex (or naked) domain when the domain is not managed by Hypernode, is to use the direct IP address of your Hypernode. You can find your IP with the `ping example.hypernode.io` command.
-
-Some DNS providers, like [DNSimple](https://dnsimple.com/) or [DNS Made Easy](http://www.dnsmadeeasy.com/), can create ALIAS or ANAME pseudo-records. These behave like CNAME records for apex domains. Unfortunately, they are not widespread yet, so the chances are your provider doesn’t support them.
-
-Another solution is redirecting traffic for the apex domain example.com to its www-counterpart [www.example.com](http://www.example.com). You can use our free wwwizer service for this. Just configure the following A-records for your apex domain, and they will redirect all traffic for you.
-
-```
-# Add both for redundancy!
-example.com A 46.21.232.141
-example.com A 46.21.233.172
-```
-
-**Please note**: Note that if you make use of the wwwizer redirect servers, people that visit <https://example.com> directly will get an error message, either indicating that there is no https available or a plain connection refused error. The wwwizers work as a forwarding service to the direct IP address of the Hypernode. This way, we can manage any IP changes for you. That is the advantage. The disadvantage is that these records do not cooperate with SSL and that, therefore the certificate does not work correctly on the domain name without the www.
-
-### Let's Encrypt and Wwwizers
-
-Also important to note is that [Let's Encrypt](../ssl/how-to-use-lets-encrypt-on-hypernode.md) does not work when you use the wwwizers, the Let's Encrypt validation cannot be completed and will return an error. The solution is to purchase a paid SSL certificate via us or to use the direct IP of your Hypernode instead.
-
-Don’t fancy these solutions? Migrate your domain to Hypernode and let us manage your DNS.
-
 ## 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.
@@ -145,7 +115,7 @@ You can read how this works [in this article](../nginx/how-to-redirect-from-or-t
 
 ## 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`, 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:
+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

docs/hypernode-platform/nginx/how-to-redirect-from-or-to-www.md

@@ -18,8 +18,6 @@ Many constructions are possible when it gets to the base URL. Some shop owners p
 
 There are some restrictions when choosing your base URL.
 
-If you use the wwwizer servers, which are sometimes used when your domain is not hosted at Hypernode and thus the DNS can’t be automagically changed in case of up or downgrades, your domain will always redirect to [www](http://www).
-
 More info can be found [on our page about setting your DNS](../dns/how-to-manage-your-dns-settings-for-hypernode.md).
 
 ## Redirect From Apex to WWW

docs/hypernode-platform/ssl/how-to-use-ssl-certificates-on-your-hypernode-when-ordered-via-hypernode-com.md

@@ -141,13 +141,6 @@ All files in /data/web/nginx starting with public.\* will be included in front o
 - Don’t forget to point the DNS for your domain to your Hypernode. More information about how this is done can be found in the article DNS settings Hypernode.
 - You will need a storefront in Magento with a secure_base_url. Otherwise Magento will redirect you to the main store. You can change the base urls using the script mentioned above, you can also do this using the following support documentation.
 
-## SSL on Your (non-www) Naked Domain While Using the Www-izer
-
-If you use the www-izer forwarders in the DNS settings for your domain name, people that visit [https://example.com](https://example.com) directly will get an error message, either indicating that there is no https available or a plain connection refused error.
-If Hypernode manages your DNS, or you’ve configured your DNS to point directly to the Hypernode, this will not be a problem.
-
-For more information please read the article DNS Settings Hypernode
-
 ## Enable SSL Stapling
 
 To enable SSL Stapling for your SSL certificate, create the following configuration in /data/web/nginx/http.ocsp:

docs/services/control-panel/how-to-use-the-dns-check.md

@@ -75,21 +75,7 @@ This means that [www.example.com](http://www.example.com) will point to wherever
 
 ### A Record
 
-One way to redirect your apex (or naked) domain, when the domain is not hosted on the Hypernode name servers, is to use the www-izers:
-
-|                                       |          |         |               |
-| ------------------------------------- | -------- | ------- | ------------- |
-| **Label**                             | **Type** | **TTL** | **Content**   |
-| [example.com](http://www.example.com) | A        | 600     | 46.21.232.141 |
-| [example.com](http://www.example.com) | A        | 600     | 46.21.233.172 |
-
-Add both for redundancy!
-
-This is the preferred way for the DNS Check because if for whatever reason the IP of your Hypernode changes, your shop will still be reachable.
-
-**NB:** Note that if you make use of the www-izer redirect servers, users that visit <https://example.com> directly will get an error message, either indicating that there is no HTTPS available or a plain connection refused error. The www-izers actually work as a forwarding service to the direct IP address of the Hypernode. This way we can manage any IP changes for you. That is the advantage, the disadvantage is that these records do not cooperate with SSL and that therefore the certificate does not work properly on the domain name without the [www.](http://www.%C2%A0)
-
-It's also an option to use the direct IP address of your Hypernode. You can find your IP with the “ping example.hypernode.io” command.
+To point your apex (or naked) domain to your Hypernode when the domain is not hosted on the Hypernode name servers, use the direct IP address of your Hypernode. You can find your IP with the `ping example.hypernode.io` command.
 
 |                                       |          |         |                      |
 | ------------------------------------- | -------- | ------- | -------------------- |