<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 18. Master/Slave operation & replication</title><link rel="stylesheet" href="docbook.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /><link rel="home" href="index.html" title="PowerDNS manual" /><link rel="up" href="index.html" title="PowerDNS manual" /><link rel="prev" href="recursor-design-and-engineering.html" title="8. Design and Engineering of the PowerDNS Recursor" /><link rel="next" href="slave.html" title="2. Slave operation" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 18. Master/Slave operation & replication</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="recursor-design-and-engineering.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="slave.html">Next</a></td></tr></table><hr /></div><div class="chapter" title="Chapter 18. Master/Slave operation & replication"><div class="titlepage"><div><div><h2 class="title"><a id="replication"></a>Chapter 18. Master/Slave operation & replication</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="replication.html#native-replication">1. Native replication</a></span></dt><dt><span class="sect1"><a href="slave.html">2. Slave operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="slave.html#supermaster">2.1. Supermaster automatic provisioning of slaves</a></span></dt><dt><span class="sect2"><a href="slave.html#lua-axfr-script">2.2. Modifying a slave zone using a script</a></span></dt></dl></dd><dt><span class="sect1"><a href="master.html">3. Master operation</a></span></dt></dl></div><p>
PDNS offers full master and slave semantics for replicating domain information. Furthermore, PDNS can benefit from native
database replication.
</p><div class="sect1" title="1. Native replication"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="native-replication"></a>1. Native replication</h2></div></div></div><p>
Native replication is the default, unless other operation is specifically configured. Native replication basically means that PDNS will
not send out DNS update notifications, nor will react to them. PDNS assumes that the backend is taking care of replication unaided.
</p><p>
MySQL replication has proven to be very robust and well suited, even over transatlantic connections between badly peering ISPs. Other PDNS
users employ Oracle replication which also works very well.
</p><p>
To use native replication, configure your backend storage to do the replication and do not configure PDNS to do so.
</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="recursor-design-and-engineering.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="slave.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">8. Design and Engineering of the PowerDNS Recursor </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2. Slave operation</td></tr></table></div></body></html>
