[Pdns-users] PowerDNS in an ISP environment

Leen Besselink leen at consolejunkie.net
Wed Aug 17 22:58:19 UTC 2011

On 08/16/2011 09:42 PM, Erik Weber wrote:
> On Tue, Aug 16, 2011 at 8:29 PM, Anthony Eden <anthonyeden at gmail.com> wrote:
>> On Tue, Aug 16, 2011 at 8:23 PM, Posner, Sebastian <s.posner at telekom.de>
>> wrote:
>>> Erik Weber wrote:
>>>>> Some other things to consider why running PDNS is better:
>>> [...]
>>>> Just shooting in with a feature that I just came to remember.
>>>> 6) Fancy records.
>>> 3.0 doesn't support fancy records any more.
>> I, for one, am sad about this.
> We're still running PowerDNS 2.x and haven't faced this change yet.
> Shouldn't it be a matter of extending the records table with a column
> with the URL information, and just insert the record as a normal A
> record?
> Your management software and the forwarding software would have to
> confront the URL field, but to PowerDNS it should look like a normal
> record.

I've never seen the need for the use of any 'special' record for
redirects. I prefer simple, hopefully future prove, solutions.

We used a seperate table from the start in the same database as PowerDNS
uses* so the management software does not need 2 databases and can join
some tables if needed. We just have the management software insert the
A-record for the redirect normally.

We also allow for redirects in the table which don't have a domain our
DNS. Sometimes it is easier to point an external domain at your own
redirect than to convince an other provider to do the redirect.

It keeps our DNS clean.

PowerDNS doesn't mind if there is an extra table (I think it doesn't
mind extra columns as you mentioned above either).

Hope that helps,

* Or actually the management software works on the master database,
PowerDNS and redirect use slave databases.

More information about the Pdns-users mailing list