From 51179a933cde64774fe25598b195ed20be2c69c9 Mon Sep 17 00:00:00 2001 From: mpana Date: Mon, 5 Mar 2018 17:28:21 +0200 Subject: [PATCH] initial dns page --- en/docs/dns.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 en/docs/dns.md diff --git a/en/docs/dns.md b/en/docs/dns.md new file mode 100644 index 0000000..65d2051 --- /dev/null +++ b/en/docs/dns.md @@ -0,0 +1,28 @@ +# DNS + +> The Container Name Service is currently not enabled for public use. + +## Overview +Spearhead Container Name Service (CNS) is a completely automatic, universal DNS for your containers and VMs on Spearhead Cloud. It is tightly integrated with Spearhead Cloud to eliminate complexity and simplify operations. + +Spearhead CNS serves address records (both A and AAAA) for containers by instance name and tags. Multiple containers providing the same service can share the same tag and will be returned in the same address record. Because Spearhead CNS knows when containers are started or stopped, including unexpected stops, the DNS information is automatically updated and requests will be sent to running containers. + +## + +Spearhead CNS offers two facilities: + +1. Serving address records for instances by instance name. +2. Serve address records for instances grouped by service label/tag (multiple instances are listed in one DNS name, depending on their availability) + +Once activated, running instances in Spearhead Compute Service with public network interfaces will be available in DNS using the following FQDN patterns: + +.inst...spearhead.cloud +.svc...triton.zone + +When activated for an account, running instances in Spearhead Compute Service with private network interfaces will be available in DNS and accessible inside the data center using the following FQDN patterns: + +.inst...spearhead.systems +.svc...cns.spearhead.systems + + +All the DNS names for an instance can be found in the instance details in Cloud Portal or via the Spearhead Cloud Tool (```spearhead get ```).