Or you can employ pipebackend or remotebackend if you don't want to write the backend completely yourself. These provide script-based API to use, which can be easier to employ than writing a backend. Documentation for these can be found from http://doc.powerdns.com/. If you need DNSSEC, you'll want to use remotebackend, as pipe can't do DNSSEC.
Aki On Mon, Feb 04, 2013 at 08:36:38AM +0100, Ruben d'Arco wrote: > Hi, > > This should be helpful as a first start: > http://doc.powerdns.com/backend-writers-guide.html > > Also have a look at the regression-test direcory, as it is quiet helpul for > testing your backend. > > Regards, > Ruben > > RBK1001 <paul....@syniverse.com> wrote: > > > > >Hi > > > >we would like to seek for an advice on the use of backend. > > > >we understood that PowerDNS offers several backend solutions, however, > >I > >would like to know is there a way to connect to our customerized > >backend? > >Currently, we are using a non-sql customerized backend with large > >amount of > >data stored, and we would like to intergrate powerdns with it, is there > >anyway we can do? > > > >- rbk > > -- > Regards, > Ruben > _______________________________________________ > Pdns-users mailing list > Pdns-users@mailman.powerdns.com > http://mailman.powerdns.com/mailman/listinfo/pdns-users >
signature.asc
Description: Digital signature
_______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
