---
title: Example configuration
description: This example configures synchronization through a proxy and uses two endpoints consisting of a PingDirectoryProxy server with a backend set of PingDirectory servers. Both sets are replicated.
component: pingdirectory
version: 11.0
page_id: pingdirectory:pingdatasync_server_administration_guide:pd_sync_example_config
canonical_url: https://docs.pingidentity.com/pingdirectory/11.0/pingdatasync_server_administration_guide/pd_sync_example_config.html
revdate: September 13, 2023
---

# Example configuration

This example configures synchronization through a proxy and uses two endpoints consisting of a PingDirectoryProxy server with a backend set of PingDirectory servers. Both sets are replicated.

The PingDirectoryProxy server uses an entry-balancing environment for the distinguished name (DN) *(tooltip: \<div class="paragraph">
\<p>A name uniquely identifying an object within the hierarchy of a directory tree.\</p>
\</div>)* `ou=People,dc=example,dc=com` and provides a subtree view for `dc=example,dc=com` in its client connection policy. For this example, communication is over standard Lightweight Directory Access Protocol (LDAP) *(tooltip: \<div class="paragraph">
\<p>An open, cross platform protocol used for interacting with directory services.\</p>
\</div>)* and failover servers are not installed or designated in PingDataSync.

![A diagram illustrating an example synchronization through proxy configuration.](_images/oga1564012179745.png)
