<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>amazondns on CoreDNS: DNS and Service Discovery</title>
    <link>https://coredns.io/tags/amazondns/</link>
    <description>Recent content in amazondns on CoreDNS: DNS and Service Discovery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>CoreDNS - All Rights Reserved</copyright>
    <lastBuildDate>Tue, 06 Mar 2018 20:32:00 +0900</lastBuildDate><atom:link href="https://coredns.io/tags/amazondns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>amazondns</title>
      <link>https://coredns.io/explugins/amazondns/</link>
      <pubDate>Tue, 06 Mar 2018 20:32:00 +0900</pubDate>
      
      <guid>https://coredns.io/explugins/amazondns/</guid>
      <description>Description The amazondns plugin behaves Authoritative name server using Amazon DNS Server as the backend.
The Amazon DNS server is used to resolve the DNS domain names that you specify in a private hosted zone in Route 53. However, the server acts as Caching name server. Although CoreDNS has proxy plugin and we can configure Amazon DNS server as the backend, it can&amp;rsquo;t be Authoritative name server. In my case, Authoritative name server is required to handle delegated responsibility for the subdomain.</description>
    </item>
    
  </channel>
</rss>
