<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ldap on OCD</title>
    <link>https://www.obsessivecomputingdisorder.com/tags/ldap/</link>
    <description>Recent content in ldap on OCD</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Adam Mendlik</copyright>
    <lastBuildDate>Mon, 27 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.obsessivecomputingdisorder.com/tags/ldap/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Load Balancing FreeIPA LDAP Servers</title>
      <link>https://www.obsessivecomputingdisorder.com/posts/load-balancing-freeipa-ldap-dns/</link>
      <pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.obsessivecomputingdisorder.com/posts/load-balancing-freeipa-ldap-dns/</guid>
      
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;
&lt;p&gt;In a multi-server FreeIPA deployment, clients typically connect to LDAP services using individual server hostnames. However, to achieve load balancing and automatic failover, you can configure a single DNS name that resolves to all your FreeIPA LDAP servers. This allows clients to connect using one consistent name, while DNS or load balancers distribute the load and handle failovers.&lt;/p&gt;
&lt;h2 id=&#34;purpose&#34;&gt;Purpose&lt;/h2&gt;
&lt;p&gt;The primary purpose of this technique is to provide automatic failover for clients. If one FreeIPA server becomes unavailable, clients can seamlessly connect to another server without manual reconfiguration. Additionally, by distributing connections across multiple servers, you can share the load and improve performance.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
