<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>rewrite on CoreDNS: DNS and Service Discovery</title>
    <link>https://coredns.io/tags/rewrite/</link>
    <description>Recent content in rewrite on CoreDNS: DNS and Service Discovery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>CoreDNS - All Rights Reserved</copyright>
    <lastBuildDate>Fri, 06 Mar 2026 16:27:00 +0000</lastBuildDate><atom:link href="https://coredns.io/tags/rewrite/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>rewrite</title>
      <link>https://coredns.io/plugins/rewrite/</link>
      <pubDate>Fri, 06 Mar 2026 16:27:00 +0000</pubDate>
      
      <guid>https://coredns.io/plugins/rewrite/</guid>
      <description>Description Rewrites are invisible to the client. There are simple rewrites (fast) and complex rewrites (slower), but they&amp;rsquo;re powerful enough to accommodate most dynamic back-end applications.
Syntax A simplified/easy-to-digest syntax for rewrite is&amp;hellip;
rewrite [continue|stop] FIELD [TYPE] [(FROM TO)|TTL] [OPTIONS] FIELD indicates what part of the request/response is being re-written.
type - the type field of the request will be rewritten. FROM/TO must be a DNS record type (A, MX, etc.</description>
    </item>
    
  </channel>
</rss>
