Merge pull request #3851 from uselagoon/dns-generic

Remove amazee.io DNS changes from the going live page

docs/README.md

@@ -40,7 +40,7 @@ Chat with us on the Lagoon Discord: [https://discord.gg/te5hHe95JE](https://disc
 
 ## A couple of things about Lagoon
 
-1. **Lagoon is based on microservices**. The deployment and build workflow is very complex. We have multiple version control sources, multiple clusters, and multiple notification systems. Each deployment is unique and can take from seconds to hours. It's built with flexibility and robustness in mind. Microservices communicate through a messaging system, which allows us to scale individual services up and down. It allows us to survive down times of individual services. It also allows us to try out new parts of Lagoon in production without affecting others.
+1. **Lagoon is based on microservices**. The deployment and build workflow is very complex. We have multiple version control sources, multiple clusters, and multiple notification systems. Each deployment is unique and can take from seconds to hours. It's built with flexibility and robustness in mind. Microservices communicate through a messaging system, which allows us to scale individual services up and down. It allows us to survive downtimes of individual services. It also allows us to try out new parts of Lagoon in production without affecting others.
 2. **Lagoon uses many programming languages**. Each programming language has specific strengths. We try to decide which language makes the most sense for each service. Currently, a lot of Lagoon is built in Node.js. This is partly because we started with Node.js, but also because Node.js allows asynchronous processing of webhooks, tasks and more. We are likely going to change the programming language of some services. This is what is great about microservices! We can replace a single service with another language without worrying about other parts of the platform.
 3. **Lagoon is not Drupal-specific**. Everything has been built so that it can run any Docker image. There are existing Docker images for Drupal, and support for Drupal-specific tools like Drush. But that's it!
 4. **Lagoon is DevOps**. It allows developers to define the services they need and customize them as they need. You might think this is not the right way to do it, and gives too much power to developers. We believe that as system engineers, we need to empower developers. If we allow developers to define services locally, and test them locally, they will find bugs and mistakes themselves.

docs/using-lagoon-the-basics/going-live.md

@@ -6,9 +6,9 @@ Congratulations, you're _this_ close to going live with your website on Lagoon!
 
 ### Routes / SSL
 
-Check to be sure that all routes have been set up in your `.lagoon.yml`. Be aware that if you don't point the domains towards Lagoon, you should disable Let's Encrypt \(LE\) certificate creation, as it will lead to issues. Domains not pointing towards Lagoon will be disabled after a while in order to not exceed the Let's Encrypt quotas.
+Check to be sure that all routes have been set up in your `.lagoon.yml`. Be aware that if you don't point the domains towards Lagoon, you should disable Let's Encrypt (LE) certificate creation, as it will lead to issues. Domains not pointing towards Lagoon will be disabled after a while in order to not exceed the Let's Encrypt quotas.
 
-If you use Certificate Authority \(CA\) signed certificates, you can set `tls-acme` to `false` , but leave the `insecure` flag set to `Allow` or `Redirect`. In the case of CA certificates, contact {{ defaults.helpstring }} with the routes and the SSL certificate that needs to be put in place.
+If you use Certificate Authority (CA) signed certificates, you can set `tls-acme` to `false` , but leave the `insecure` flag set to `Allow` or `Redirect`. In the case of CA certificates, contact {{ defaults.helpstring }} with the routes and the SSL certificate that needs to be put in place.
 
 ```yaml title=".lagoon.yml"
 environments:
@@ -51,35 +51,9 @@ Check if your cron jobs have been set up for your production environment - see [
 
 ## DNS
 
-To make it as smooth as possible for you to get your site pointing to our servers, we have dedicated load-balancer DNS records. Those technical DNS resource records are used for getting your site linked to the amazee.io infrastructure and serve no other purpose. If you are in doubt of the CNAME record, contact {{ defaults.helpstring }} about the exact CNAME you need to set up.
+You will need to update your DNS to point at your Lagoon hosting providers servers (e.g. their CDN or load balancers). Please contact {{ defaults.helpstring }} for more information.
 
-**Example on amazee.io :** `<region-identifier>.amazee.io`
-
-Before you switch over your domain to Lagoon, make sure you lower the Time-to-Live \(TTL\) before you go live. This will ensure that the switch from the old to the new servers will go quickly. We usually advise a TTL of 300-600 seconds prior to the DNS switch. [More information about TTL](https://en.wikipedia.org/wiki/Time_to_live#DNS_records).
-
-!!! Info
-    This information only relates to amazee.io hosted projects, and will shortly be removed from these docs and added to amazee.io specific ones
-
-### Recommended settings for Fastly:
-
-#### Subdomains (CNAME)
-The recommended method of pointing your subdomain's \(e.g. www.example.com\) DNS records at Lagoon is via a CNAME record as shown below:
-<!-- markdown-link-check-disable-next-line -->
-`CNAME`: `cdn.amazee.io`
-
-#### Root domains (A/AAAA)
-
-Configuring the root domain \(e.g. example.com.\) can be tricky because the DNS specification does not allow root domains to point to a CNAME. Therefore, the following A and AAAA records should be used. Please ensure you set up individual records for each IP listed below:
-
-* `A`: `151.101.2.191`
-* `A`: `151.101.66.191`
-* `A`: `151.101.130.191`
-* `A`: `151.101.194.191`
-
-* `AAAA`: `2a04:4e42::703`
-* `AAAA`: `2a04:4e42:200::703`
-* `AAAA`: `2a04:4e42:400::703`
-* `AAAA`: `2a04:4e42:600::703`
+Before you switch over your domain to Lagoon, make sure you lower the Time-to-Live (TTL) before you go live. This will ensure that the switch from the old to the new servers will go quickly. We usually advise a TTL of 300 seconds prior to the DNS switch. [More information about TTL](https://en.wikipedia.org/wiki/Time_to_live#DNS_records).
 
 ## Production environment