Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-10-27 08:14:18 -04:00
Code Issues Packages Projects Releases Wiki Activity

plugin/clouddns: tiny fixes for the README (#3140)

Browse Source 
* plugin/clouddns: tiny fixes for the README

Did a post-merge review. Fix a few typos.

Signed-off-by: Miek Gieben <miek@miek.nl>

* Naming;

coredns -> CoreDNS
clouddns -> Cloud DNS
and italics then the plugin's name are mentioned.

Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
Miek Gieben
2019-08-18 08:40:34 +00:00
committed by GitHub
parent b53d822e62
commit bbc78abf6f
1 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
plugin/clouddns/README.md
View File

@@ -2,17 +2,18 @@
## Name
*clouddns* - enables serving zone data from GCP clouddns.
*clouddns* - enables serving zone data from GCP Cloud DNS.
## Description
The clouddns plugin is useful for serving zones from resource record sets in GCP clouddns.
This plugin supports all [Google Cloud DNS records](https://cloud.google.com/dns/docs/overview#supported_dns_record_types).
The clouddns plugin can be used when coredns is deployed on GCP or elsewhere. Note that
this plugin access the the resource records through Google Cloud API. For records in a
privately hosted zone, it is not necessary to place CoreDNS and this plugin in associated
VPC network. In fact the private hosted zone could be created without any associated VPC
and this plugin could still access the resource records under the hosted zone.
The *clouddns* plugin is useful for serving zones from resource record
sets in GCP Cloud DNS. This plugin supports all [Google Cloud DNS
records](https://cloud.google.com/dns/docs/overview#supported_dns_record_types). This plugin can
be used when CoreDNS is deployed on GCP or elsewhere. Note that this plugin accesses the resource
records through the Google Cloud API. For records in a privately hosted zone, it is not necessary to
place CoreDNS and this plugin in the associated VPC network. In fact the private hosted zone could
be created without any associated VPC and this plugin could still access the resource records under
the hosted zone.
## Syntax