<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd"> <HTML ><HEAD ><TITLE >Modules & Backends</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK REL="HOME" TITLE="PowerDNS manual" HREF="index.html"><LINK REL="UP" TITLE="PDNS internals" HREF="pdns-internals.html"><LINK REL="PREVIOUS" TITLE="Guardian" HREF="guardian.html"><LINK REL="NEXT" TITLE="How PDNS translates DNS queries into backend queries" HREF="dns-to-query.html"></HEAD ><BODY CLASS="SECT1" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#840084" ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="3" ALIGN="center" >PowerDNS manual</TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A HREF="guardian.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" >Appendix B. PDNS internals</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A HREF="dns-to-query.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="MODULES" >B.3. Modules & Backends</A ></H1 ><P > PDNS has the concept of backends and modules. Non-static PDNS distributions have the ability to load new modules at runtime, while the static versions come with a number of modules built in, but cannot load more. </P ><P > Related parameters are: <P ></P ><DIV CLASS="VARIABLELIST" ><DL ><DT >--help</DT ><DD ><P > Outputs all known parameters, including those of launched backends, see below. </P ></DD ><DT >--launch=backend,backend1,backend1:name</DT ><DD ><P > Launches backends. In its most simple form, supply all backends that need to be launched. If you find that you need to launch single backends multiple times, you can specify a name for later instantiations. In this case, there are 2 instances of backend1, and the second one is called 'name'. This means that <B CLASS="COMMAND" >--backend1-setting</B > is available to configure the first or main instance, and <B CLASS="COMMAND" >--backend1-name-setting</B > for the second one. </P ></DD ><DT >--load-modules=/directory/libyourbackend.so</DT ><DD ><P > If backends are available in nonstandard directories, specify their location here. Multiple files can be loaded if separated by commas. Only available in non-static PDNS distributions. </P ></DD ><DT >--list-modules</DT ><DD ><P > Will list all available modules, both compiled in and in dynamically loadable modules. </P ></DD ></DL ></DIV > To run on the commandline, use the <B CLASS="COMMAND" >pdns_server</B > binary. For example, to see options for the gpgsql backend, use the following: <PRE CLASS="SCREEN" > $ /usr/sbin/pdns_server --launch=gpgsql --help=gpgsql </PRE > </P ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="guardian.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" ACCESSKEY="H" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="dns-to-query.html" ACCESSKEY="N" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >Guardian</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="pdns-internals.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >How PDNS translates DNS queries into backend queries</TD ></TR ></TABLE ></DIV ></BODY ></HTML >