First draft of Cloudflare articles

en/cloudflare-service/cloudflare-add-a-dns-record.md

@@ -0,0 +1,41 @@
+---
+title: "Cloudflare: Add a DNS record"
+slug: cloudflare-add-dns-record
+---
+
+
+## About this task
+
+This article will guide you through the process of adding a new DNS record to a Cloudflare DNS domain.
+
+## Before you begin
+
+-   Your Cloudflare environment must already exist
+-   The target domain must already exist in the environment
+-   The registrar where this domain name is hosted must point to the Cloudflare name servers
+-   The state of the domain must be `Active`
+
+## Procedure
+
+1.  Navigate to your Cloudflare service using the **Services** menu, click on the target environment from the service page, then click on the target domain.
+
+2.  Click the **Add DNS record** button.
+
+3.  On the **Add DNS record** page, select the record type and enter the values for your record.
+
+    Each resource record type has its own fields, therefore changing the **Type** field will change the displayed fields.
+
+4.  Select a time to live \(TTL\) value for this record.
+
+    This option controls how long a DNS client will cache the record before requesting it again from the DNS system.
+
+5.  \(Optional\) Enter a comment to be appended to the record. This is internal to the record and will not be displayed in the list of records.
+
+6.  Click the **Submit** button.
+
+
+## Results
+
+-   The new DNS record is now listed in the target domain page.
+-   The record now resolves when queried through the DNS system
+

en/cloudflare-service/cloudflare-add-a-domain.md

@@ -0,0 +1,38 @@
+---
+title: "Cloudflare: Add a domain"
+slug: cloudflare-add-domain
+---
+
+
+## About this task
+
+This article will guide you through the process of adding a new domain to a Cloudflare environment.
+
+## Before you begin
+
+-   Your Cloudflare environment must already exist
+
+## Procedure
+
+1.  Navigate to your Cloudflare service using the **Services** menu, and click on the target environment from the service page.
+
+2.  Click on the **Add Domain** button. The **Add Domain** page will appear.
+
+3.  Enter the fully qualified domain name to add.
+
+    It is not necessary to have the trailing period at the end of the domain name. The system will automatically add it for you.
+
+    Optionally, mark the **Quick Scan for Records** checkbox to have the system import any existing resource records, by querying the current name servers.
+
+4.  Click **Submit**.
+
+5.  If you marked the **Quick Scan for Records** checkbox, click on your domain when the environment page appears, and then verify that all the required resource records were successfully imported.
+
+    It is possible that some records may be missed during the scanning process. If any records are missing, add the missing records manually.
+
+
+## Results
+
+-   The domain is now listed in the target environment
+-   If importing was selected, you have verified that all records have been imported, and any missing records have been added manually
+

en/cloudflare-service/cloudflare-dns.md

@@ -0,0 +1,72 @@
+---
+title: "Cloudflare: DNS"
+slug: cloudflare-dns
+---
+
+
+This article introduces the Cloudflare DNS service, for creating and managing domains, records, and accounts through CloudOps environments.
+
+## Overview
+
+The Cloudflare DNS service provides high-performance name resolution for large-scale applications, with global distribution and reliable security. CloudOps integrates with the DNS service by enabling management of zones, including adding and deleting DNS records. This integration allows multiple zones to be administered from a single CloudOps environment.
+
+For DNS resolution to function properly, your domain must be configured at the name registrar to point to the Cloudflare name servers. Cloudflare will host the DNS records \(also known as **resource records**\) for your domain. The CloudOps interface provides a simple way to manage those resource records alongside your other cloud services.
+
+![Diagram illustrating how the major entities in CloudOps and Cloudflare are related](cloudflare-dns-entities.svg)
+
+To enhance performance and security, you may also choose to have Cloudflare proxy the traffic for your A, AAAA, and CNAME records. When a client makes a DNS query for the host name of a proxied DNS record, Cloudflare will return the IP address of its own front-end servers. When the client makes an HTTP or HTTPS request, the client will send the request to Cloudflare's servers, which will in turn make the request to the origin server, which is the server identified in your DNS record. This content will be returned in the response to the client, and will also be cached at the Cloudflare servers for faster retrieval.
+
+## Environments
+
+To begin working with Cloudflare resources, create a new environment in the Cloudflare service in CloudOps. Upon creating a new environment, a new account will be automatically created in Cloudflare, and associated to the CloudOps environment.
+
+![A screenshot of the Environments page for the Cloudflare service](cloudflare-env-list.png)
+
+If there is an error when creating a new environment, it is possible that the Cloudflare API key used to create the service connection lacks the appropriate access. Contact your Cloudflare administrator and ensure that the master account has granted the API key with the following permissions:
+
+-   `Zone.Zone Settings`
+-   `Zone.Zone`
+-   `Zone.DNS`
+-   `Global xauth key`
+
+## Domains
+
+Clicking on an environment will take you to a list of the domains managed in that environment, where you will be able to add new domains. When adding a domain, you have the option to have the system scan your domain and import and existing resource records. After the domain is added, it will remain in the `Pending nameservers` state until the domain registrar is configured to point to the Cloudflare name servers.
+
+![Screenshot of the Domains tab of a Cloudflare environment, with highlights on key features](cloudflare-domain-list.png)
+
+1.  **List of domains**
+
+    In the main area of the workspace, a list of all domains in the selected environment appears.
+
+2.  **Search box**
+
+    Type in the search box to filter the domain list. The system will search through the name and last modified fields, and returns any domain that matches the string in the search box.
+
+3.  **Add a domain**
+
+    Click to define a domain to be hosted by Cloudflare.
+
+    Optionally, when creating the domain you may also import the existing DNS records for the target domain.
+
+4.  **Domain entry**
+
+    Each entry includes the name of the domain, the status of the domain configuration, the plan type, and the last modification date.
+
+    Click on the entry to navigate to the details page for the domain.
+
+5.  **Hidden Actions menu**
+
+    Each entry in the domain list has a Hidden Actions menu. Click on the Hidden Actions menu to access a list of frequently-used operations for the domain.
+
+
+## DNS records
+
+Click on a domain to see the current name servers and their IP addresses, and a list all its resource records.
+
+If the system detects that the domain registrar is not pointing this domain to the Cloudflare DNS servers, it will display an information message indicating that this step is required, and it will also provide the name servers and their IP addresses as they must be configured in the registrar.
+
+The list of DNS records will contain the standard fields for each resource record, and it will also show if the traffic for that host name is proxied.
+
+![Screenshot of the DNS Records page](cloudflare-dns-records.png)
+

en/cloudflare-service/cloudflare-service.md

@@ -0,0 +1,3 @@
+---
+name: Cloudflare Service
+---

layout.yaml

@@ -93,6 +93,12 @@ categories:
       - vmware-virtual-applications.md
       - vmware-add-a-network.md
       - vmware-add-a-virtual-machine.md
+- category: cloudflare-service
+  icon: fa fa-cloud
+  articles:
+      - cloudflare-dns.md
+      - cloudflare-add-a-domain.md
+      - cloudflare-add-a-dns-record.md
 - category: object-storage-service
   icon: fa fa-hdd-o
   articles: