<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ipecho on CoreDNS: DNS and Service Discovery</title><link>https://coredns.website.cncfstack.com/tags/ipecho/</link><description>Recent content in ipecho on CoreDNS: DNS and Service Discovery</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>CoreDNS - All Rights Reserved</copyright><lastBuildDate>Fri, 29 Sep 2017 16:18:35 +0100</lastBuildDate><atom:link href="https://coredns.website.cncfstack.com/tags/ipecho/index.xml" rel="self" type="application/rss+xml"/><item><title>ipecho</title><link>https://coredns.website.cncfstack.com/explugins/ipecho/</link><pubDate>Fri, 29 Sep 2017 16:18:35 +0100</pubDate><guid>https://coredns.website.cncfstack.com/explugins/ipecho/</guid><description>Description ipecho parses the IP out of a subdomain and echos it back as an record.
Example A IN 127.0.0.1.example.com. -&amp;gt; A: 127.0.0.1 AAAA IN ::1.example.com. -&amp;gt; AAAA: ::1 Syntax ipecho { domain example1.com domain example2.com ttl 2629800 } domain adds the domain that should be handled ttl defines the ttl that should be used in the response debug enables debug logging</description></item></channel></rss>