<?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 8. Virtual hosting</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="considerations.html" title="2. Considerations" /><link rel="next" href="performance.html" title="Chapter 9. Authoritative Server Performance" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 8. Virtual hosting</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="considerations.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="performance.html">Next</a></td></tr></table><hr /></div><div class="chapter" title="Chapter 8. Virtual hosting"><div class="titlepage"><div><div><h2 class="title"><a id="virtual"></a>Chapter 8. Virtual hosting</h2></div></div></div><p>
It may be advantageous to run multiple separate PDNS installations on a single host, for example to make sure
that different customers cannot affect each others zones. PDNS fully supports running multiple instances on one host.
</p><p>
To generate additional PDNS instances, copy the init.d script <code class="filename">pdns</code> to <code class="filename">pdns-name</code>,
where <code class="filename">name</code> is the name of your virtual configuration. Must not contain a - as this will confuse the
script.
</p><p>
When you launch PDNS via this renamed script, it will seek configuration instructions not in <code class="filename">pdns.conf</code>
but in <code class="filename">pdns-name.conf</code>, allowing for separate specification of parameters.
</p><p>
Be aware however that the init.d <span class="command"><strong>force-stop</strong></span> will kill all PDNS instances!
</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="considerations.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="performance.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2. Considerations </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 9. Authoritative Server Performance</td></tr></table></div></body></html>
