Merge pull request #2390 from nmelehan/rc-v0.8

[Release Candidate] v0.8

ci/vale/dictionary.txt

@@ -157,6 +157,7 @@ clickjacking
 client1
 client2
 clojure
+cloudflare
 cloudnet
 clozure
 cls
@@ -543,6 +544,7 @@ iframes
 ifup
 ikiwiki
 im
+imagize
 imap
 imapd
 imaps
@@ -1353,6 +1355,7 @@ ucd
 ufw
 ui
 uidl
+umount
 un
 unaliased
 unarchive

ci/yaml_rules.json

@@ -20,11 +20,17 @@
     "type": "dict",
     "description": "First and last names of the original guide author."
   },
+  "classic_manager_link": {
+	  "elements": false,
+	  "required": false,
+	  "type": "text",
+	  "description": "In a guide which features copy or screenshots of the new Cloud Manager, this provides a link to the older guide written for the Linode Classic Manager, if an older/classic version of the guide was previously written. The link will be included within the Linode Classic Manager banner message at the bottom of the guide. The link must be a string using the alias format (platform/example-guide-classic-manager). Both the classic_manager_link and cloud_manager_link should be used between corresponding guides to create a bi-directional link. Must use alias-style relative links (e.g. platform/manager/dns-manager-classic-manager/)."
+  },
   "cloud_manager_link": {
 	  "elements": false,
 	  "required": false,
 	  "type": "text",
-	  "description": "In a guide written for the current Linode Manager, if a new version of the guide exists written for the new Linode Manager, use this in the original guide to embed a link to the new guide. Must use alias-style relative links (e.g. platform/manager/dns-manager-cloud-manager/)."
+	  "description": "In a guide which features copy or screenshots of the Linode Classic Manager, this provides a link to a guide written for the new Cloud Manager, if a new version of the guide has been written. The link will be included within the Cloud Manager banner message at the top of the guide. The link must be a string using the alias format (platform/example-guide). Both the classic_manager_link and cloud_manager_link should be used between corresponding guides to create a bi-directional link. Must use alias-style relative links (e.g. platform/manager/dns-manager/)."
   },
   "concentrations": {
     "elements": false,

docs/getting-started/index.md

@@ -18,6 +18,7 @@ type: "guide"
 weight: 10
 icon: "book"
 show_on_rss_feed: false
+classic_manager_link: getting-started-classic-manager/
 ---
 
 ![Getting Started with Linode](getting-started.jpg "Getting Started with Linode")
@@ -28,10 +29,6 @@ Thank you for choosing Linode as your cloud hosting provider! This guide will he
 
 From there you'll set up a Linux distribution, boot your Linode, and perform some basic system administration tasks. If you've already created an account and booted your Linode, skip ahead to [connecting to your Linode](#connect-to-your-linode-via-ssh) using SSH.
 
-{{< note >}}
-View the Linode Classic Manager version of the [Getting Started](/docs/getting-started-classic-manager/) guide.
-{{</ note >}}
-
 <!-- removing the video for now to test if gifs are more helpful
 <div class="wistia_responsive_padding" style="padding:56.25% 0 0 0;position:relative;"><div class="wistia_responsive_wrapper" style="height:100%;left:0;position:absolute;top:0;width:100%;"><iframe src="//fast.wistia.net/embed/iframe/35724r19mr?videoFoam=true" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="100%" height="100%"></iframe></div></div><script src="//fast.wistia.net/assets/external/E-v1.js" async></script>
 -->

docs/networking/dns/common-dns-configurations-classic-manager/index.md

@@ -0,0 +1,55 @@
+---
+author:
+  name: Linode
+  email: docs@linode.com
+description: 'Configurations for common DNS records.'
+og_description: 'This guide explains how to use the Linode DNS manager, to configure DNS records'
+keywords: ["dns", "dnssec"]
+license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
+aliases: ['dns-manager/','dns-guides/configuring-dns-with-the-linode-manager/']
+modified: 2019-01-28
+modified_by:
+  name: Linode
+published: 2015-01-20
+title: Common DNS Configurations
+hiddenguide: true
+cloud_manager_link: 'networking/dns/common-dns-configurations/'
+---
+
+![Common DNS Configurations](common-dns-configurations-title-graphic.jpg "Common DNS Configurations")
+
+## Set Up a Domain
+
+The most common DNS configuration is a single domain name on a single Linode. For this, you'll need to add *SOA* and *NS records* for all of your name servers, and *A/AAAA* records for your domain names. Use the screenshot below as a guide.
+
+[![The SOA record is set to "ns1.linode.com". The NS records are set to "ns1.linode.com" through "ns5.linode.com", inclusive. The MX record is set to "mail.example.org". There are A records for [blank], which is the primary domain, and the "mail" and "www" subdomains. They are all set to the same IP.](1121-dns9.png)](1121-dns9.png)
+
+ {{< note >}}
+The DNS Manager can automatically add all of these records when you create a domain zone. For instructions, see [Adding Domain Zones](/docs/networking/dns/dns-manager#add-a-domain-zone) in the [DNS Manager](/docs/networking/dns/dns-manager) guide.
+{{< /note >}}
+
+## Configure Subdomains
+
+To configure a subdomain, such as `staging.example.org`, create an A record with the subdomain's hostname. Point the record at the IP address of the server you want to host the subdomain:
+
+[![Create a new A record, following the instructions in the "Adding" section. Add the subdomain text to the "Hostname" field. For example, you could type "staging" - NOT "staging.example.org".](1125-dns13.png)](1125-dns13.png)
+
+## Host Multiple Domains on a Single Server
+
+To host multiple domain names on a single server, create a separate domain zone for each domain name as shown below. When creating the new domain zones, we recommend that you allow the DNS Manager to automatically [insert basic records](/docs/networking/dns/dns-manager#add-a-domain-zone). At a minimum, you'll need an A record for each domain name pointing to the server's IP address.
+
+[![This page shows the DNS Manager tab with three different domain zones listed.](1126-dns15.png)](1126-dns15.png)
+
+## Use One Domain on Multiple Servers
+
+If you have more than one server, but only one domain name, you can point A records with server-specific hostnames to all servers that need domain names. One machine will be the "front end" for the domain, by virtue of the first-level domain's A record pointing to it, but the domain can serve as a proxy for services provided by other machines if needed. For example, if you wanted to create a development environment on another server, you could create an A record for `staging.example.org` and point it at another Linode's IP address.
+
+## Route Email to Third-Party Mail Services
+
+To route email to a third-party email service, create MX records that associate your mail server (for example, `mail.example.org`) with a *hostname* provided by the third-party service. For instructions, see the website of your third-party email service.
+
+## Use Wildcard DNS Records
+
+A *wildcard* DNS record matches requests for non-existent domain names. For example, if you create an A record for `*.example.org`, and a user visits `nonexistantname.example.org`, that user will be redirected to `example.org`. An example wildcard DNS record is shown below.
+
+[![Create a new A record, following the instructions in the "Adding" section. Add a single asterisk (\*) in the "Hostname" field. Set your IP address in the "IP Address" field. Then click the "Save Changes" button.](1127-dns16.png)](1127-dns16.png)

docs/networking/dns/common-dns-configurations/index.md

@@ -3,15 +3,16 @@ author:
   name: Linode
   email: docs@linode.com
 description: 'Configurations for common DNS records.'
-og_description: 'This guide explains how to use the Linode DNS manager, to configure DNS records'
+og_description: 'This guide explains how to use the Linode Cloud Manger to configure DNS records'
 keywords: ["dns", "dnssec"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['dns-manager/','dns-guides/configuring-dns-with-the-linode-manager/']
-modified: 2019-01-28
+modified: 2019-03-14
 modified_by:
   name: Linode
 published: 2015-01-20
 title: Common DNS Configurations
+classic_manager_link: 'networking/dns/common-dns-configurations-classic-manager/'
 ---
 
 ![Common DNS Configurations](common-dns-configurations-title-graphic.jpg "Common DNS Configurations")
@@ -20,34 +21,46 @@ title: Common DNS Configurations
 
 The most common DNS configuration is a single domain name on a single Linode. For this, you'll need to add *SOA* and *NS records* for all of your name servers, and *A/AAAA* records for your domain names. Use the screenshot below as a guide.
 
-[![The SOA record is set to "ns1.linode.com". The NS records are set to "ns1.linode.com" through "ns5.linode.com", inclusive. The MX record is set to "mail.example.org". There are A records for [blank], which is the primary domain, and the "mail" and "www" subdomains. They are all set to the same IP.](1121-dns9.png)](1121-dns9.png)
+[![The SOA record is set to "example-site-demo.com". The NS records are set to "ns1.linode.com" through "ns5.linode.com", inclusive. The MX record is set to "mail.example-site-demo.com". There are A records for [blank], which is the primary domain, and the "mail" and "www" subdomains. They are all set to the same IP.](common-dns-set-up-a-domain.png)](common-dns-set-up-a-domain.png)
 
  {{< note >}}
-The DNS Manager can automatically add all of these records when you create a domain zone. For instructions, see [Adding Domain Zones](/docs/networking/dns/dns-manager#add-a-domain-zone) in the [DNS Manager](/docs/networking/dns/dns-manager) guide.
+The Domains section of the Cloud Manager can automatically add all of these records when you create a domain. For instructions, see the *Add a Domain* section of the [DNS Manager](/docs/networking/dns/dns-manager) guide.
 {{< /note >}}
 
 ## Configure Subdomains
 
-To configure a subdomain, such as `staging.example.org`, create an A record with the subdomain's hostname. Point the record at the IP address of the server you want to host the subdomain:
+1.  To configure a subdomain (e.g. `staging.example-site-demo.com`), create an A record with the subdomain's hostname. Click **Add an A/AAA Record**:
 
-[![Create a new A record, following the instructions in the "Adding" section. Add the subdomain text to the "Hostname" field. For example, you could type "staging" - NOT "staging.example.org".](1125-dns13.png)](1125-dns13.png)
+    [![Create a new A record by first click on "Add an A/AAA Record"](common-dns-add-an-a-record.png)](common-dns-add-an-a-record.png)
+
+1.  Add the subdomain under the **Hostname** field. Assign the IP address of the server you want to host the subdomain:
+
+    [![Create a new A record, following the instructions in the "Adding" section. Add the subdomain text to the "Hostname" field. For example, you could type "staging" - NOT "staging.example-site-demo.com".](common-dns-add-an-a-record-menu.png)](common-dns-add-an-a-record-menu.png)
+
+1. Click on the **Save** button to create the record.
+
+    {{< disclosure-note "Multi-level Subdomains" >}}
+The Linode Cloud Manager does not support adding a subdomain of a subdomain in the same domain zone. For example, if you have `example.com` as a domain with an A record for `staging.example.com`, you cannot create `test.staging.example.com` within that same domain zone. Instead, create a separate domain zone for the subdomain `staging.example.com`. Then, add an A record for `test.staging.example.com` to that new zone.
+
+See the [subdomains](/docs/platform/manager/dns-manager/#subdomains) section of the [DNS manager](/docs/platform/manager/dns-manager/#subdomains) guide for more information.
+    {{</ disclosure-note >}}
 
 ## Host Multiple Domains on a Single Server
 
-To host multiple domain names on a single server, create a separate domain zone for each domain name as shown below. When creating the new domain zones, we recommend that you allow the DNS Manager to automatically [insert basic records](/docs/networking/dns/dns-manager#add-a-domain-zone). At a minimum, you'll need an A record for each domain name pointing to the server's IP address.
+To host multiple domain names on a single server, create a separate domain entry for each domain name as shown below. When creating the new domain entry, we recommend that you allow the Domains section of the Cloud Manager to automatically [insert basic records](/docs/networking/dns/dns-manager#add-a-domain-zone). At a minimum, you'll need an A record for each domain name pointing to the server's IP address.
 
-[![This page shows the DNS Manager tab with three different domain zones listed.](1126-dns15.png)](1126-dns15.png)
+[![This page shows the Domains page with three different domain zones listed.](common-dns-multiple-domains-one-server.png)](common-dns-multiple-domains-one-server.png)
 
 ## Use One Domain on Multiple Servers
 
-If you have more than one server, but only one domain name, you can point A records with server-specific hostnames to all servers that need domain names. One machine will be the "front end" for the domain, by virtue of the first-level domain's A record pointing to it, but the domain can serve as a proxy for services provided by other machines if needed. For example, if you wanted to create a development environment on another server, you could create an A record for `staging.example.org` and point it at another Linode's IP address.
+If you have more than one server, but only one domain name, you can point A records with server-specific hostnames to all servers that need domain names. One machine will be the "front end" for the domain, by virtue of the first-level domain's A record pointing to it, but the domain can serve as a proxy for services provided by other machines, if needed. For example, if you wanted to create a development environment on another server, you could create an A record for `staging.example.com` and point it at another Linode's IP address.
 
 ## Route Email to Third-Party Mail Services
 
-To route email to a third-party email service, create MX records that associate your mail server (for example, `mail.example.org`) with a *hostname* provided by the third-party service. For instructions, see the website of your third-party email service.
+To route email to a third-party email service, create MX records that associate your mail server (for example, `mail.example-site-demo.com`) with a *hostname* provided by the third-party service. For more detailed instructions, see the website of your third-party email service.
 
 ## Use Wildcard DNS Records
 
-A *wildcard* DNS record matches requests for non-existent domain names. For example, if you create an A record for `*.example.org`, and a user visits `nonexistantname.example.org`, that user will be redirected to `example.org`. An example wildcard DNS record is shown below.
+A *wildcard* DNS record matches requests for non-existent domain names. For example, if you create an A record for `*.example.com`, and a user visits `nonexistantname.example.com`, that user will be redirected to `example.com`. An example wildcard DNS record is shown below.
 
-[![Create a new A record, following the instructions in the "Adding" section. Add a single asterisk (\*) in the "Hostname" field. Set your IP address in the "IP Address" field. Then click the "Save Changes" button.](1127-dns16.png)](1127-dns16.png)
+[![Create a new A record, following the instructions in the "Adding" section. Add a single asterisk (\*) in the "Hostname" field. Set your IP address in the "IP Address" field. Then click the "Save Changes" button.](common-dns-use-wildcard.png)](common-dns-use-wildcard.png)

docs/networking/dns/configure-your-linode-for-reverse-dns-classic-manager/index.md

@@ -9,8 +9,8 @@ modified_by:
   name: Linode
 published: 2015-07-09
 title: Configure Your Linode for Reverse DNS (rDNS)
-cloud_manager_link: networking/dns/configure-your-linode-for-reverse-dns
-headless: true
+cloud_manager_link: networking/dns/configure-your-linode-for-reverse-dns/
+hiddenguide: true
 ---
 
 ![Configure Your Linode for Reverse DNS (rDNS)](configure-your-linode-reverse-dns.jpg)

docs/networking/dns/configure-your-linode-for-reverse-dns/index.md

@@ -5,19 +5,16 @@ author:
 description: 'Reverse DNS (rDNS) resolves an IP address to the designated domain name. This guide will teach you how to set it up.'
 keywords: ["reverse", "dns", "PTR"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
-aliases: ['dns-manager/','dns-guides/configuring-dns-with-the-linode-manager/','networking/dns/setting-reverse-dns/','networking/Setting-Up-Reverse-DNS-Lookup/','networking/configure-your-linode-for-reverse-dns/']
+aliases: ['networking/Setting-Up-Reverse-DNS-Lookup/','dns-guides/configuring-dns-with-the-linode-manager/','networking/configure-your-linode-for-reverse-dns/','networking/dns/setting-reverse-dns/','dns-manager/']
 modified_by:
   name: Linode
 published: 2015-07-09
 title: Configure Your Linode for Reverse DNS (rDNS)
+classic_manager_link: networking/dns/configure-your-linode-for-reverse-dns-classic-manager/
 ---
 
 ![Configure Your Linode for Reverse DNS (rDNS)](configure-your-linode-reverse-dns.jpg)
 
-{{< note >}}
-You can also view the Linode Classic Manager version of the [Configure Your Linode for Reverse DNS](/docs/networking/dns/configure-your-linode-for-reverse-dns-classic-manager/) guide.
-{{</ note >}}
-
 Computers use DNS to determine the IP address associated with a domain name. *Reverse* DNS lookup does the opposite by resolving an IP address to a designated domain name. You should always set the reverse DNS, even if your Linode hosts more than one domain.
 
 Reverse DNS uses a *pointer record* (*PTR*) to match an IP address with a domain or subdomain. PTR records are generally set with a hosting provider, so reverse DNS is set in the Linode Cloud Manager.