<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>forward on CoreDNS: DNS and Service Discovery</title>
    <link>https://coredns.io/tags/forward/</link>
    <description>Recent content in forward on CoreDNS: DNS and Service Discovery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>CoreDNS - All Rights Reserved</copyright>
    <lastBuildDate>Sat, 17 Jan 2026 06:17:00 +0000</lastBuildDate><atom:link href="https://coredns.io/tags/forward/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>forward</title>
      <link>https://coredns.io/plugins/forward/</link>
      <pubDate>Sat, 17 Jan 2026 06:17:00 +0000</pubDate>
      
      <guid>https://coredns.io/plugins/forward/</guid>
      <description>Description The forward plugin re-uses already opened sockets to the upstreams. It supports UDP, TCP and DNS-over-TLS and uses in band health checking.
When it detects an error a health check is performed. This checks runs in a loop, performing each check at a 0.5s interval for as long as the upstream reports unhealthy. Once healthy we stop health checking (until the next error). The health checks use a recursive DNS query (.</description>
    </item>
    
  </channel>
</rss>
