<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>loadbalance on CoreDNS: DNS and Service Discovery</title>
    <link>https://coredns.io/tags/loadbalance/</link>
    <description>Recent content in loadbalance on CoreDNS: DNS and Service Discovery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>CoreDNS - All Rights Reserved</copyright>
    <lastBuildDate>Tue, 09 Sep 2025 18:54:52 +0000</lastBuildDate><atom:link href="https://coredns.io/tags/loadbalance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>loadbalance</title>
      <link>https://coredns.io/plugins/loadbalance/</link>
      <pubDate>Tue, 09 Sep 2025 18:54:52 +0000</pubDate>
      
      <guid>https://coredns.io/plugins/loadbalance/</guid>
      <description>Description The loadbalance will act as a round-robin DNS load balancer by randomizing the order of A, AAAA, and MX records in the answer.
See Wikipedia about the pros and cons of this setup. It will take care to sort any CNAMEs before any address records, because some stub resolver implementations (like glibc) are particular about that.
Syntax loadbalance [round_robin | weighted WEIGHTFILE] { reload DURATION prefer CIDR [CIDR...] } round_robin policy randomizes the order of A, AAAA, and MX records applying a uniform probability distribution.</description>
    </item>
    
  </channel>
</rss>
