<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>idetcd on CoreDNS: DNS and Service Discovery</title>
    <link>https://coredns.io/tags/idetcd/</link>
    <description>Recent content in idetcd on CoreDNS: DNS and Service Discovery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>CoreDNS - All Rights Reserved</copyright>
    <lastBuildDate>Mon, 13 Aug 2018 18:54:20 +0100</lastBuildDate><atom:link href="https://coredns.io/tags/idetcd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>idetcd</title>
      <link>https://coredns.io/explugins/idetcd/</link>
      <pubDate>Mon, 13 Aug 2018 18:54:20 +0100</pubDate>
      
      <guid>https://coredns.io/explugins/idetcd/</guid>
      <description>Description idetcd is used for identifying nodes in a cluster without domain name collision.The basic idea is quite simple: Set up CoreDNS server on every node when you going to start a cluster, and node exposes itself by taking the free domain name in etcd.
Syntax idetcd { endpoint ENDPOINT... limit LIMIT pattern PATTERN } endpoint defines the etcd endpoints. Defaults to &amp;ldquo;http://localhost:2379&amp;rdquo;. limit defines the maximum limit of the node number in the cluster, if some nodes is going to expose itself after the node number in the cluster hits this limit, it will fail.</description>
    </item>
    
  </channel>
</rss>
