Nikolaos Milas wrote:
If you managed to set up this demo (Split-DNS with powerdns and LDAP-Backend)
for the "Linux-Tage", could you please post this work here or a link to a page
where it is available?
Basically it boils down to this ACL:
access to
dn.subtree="cn=pdns,ou=services,ou=infra-di
On 4/3/2015 8:17 μμ, Michael Ströder wrote:
This sounds a bit like a special case for split horizon DNS.
I promised to configure a demo using powerdns with LDAP backend for this based
on OpenLDAP ACLs and several powerdns instances using different LDAP identities.
Feel free to come here and as
On 5/3/2015 8:53 πμ, Michael Ströder wrote:
Yes, IMHO it's far easier to build up a replicated setup with the LDAP backend
than with any SQL DB.
We are using LDAP replication for powerdns (rather than normal
master-slaves) for years. It is a great setup.
>Unfortunately, Grégory Oestreicher'
Nikolaos Milas wrote:
> Despite the fact that PowerDNS with LDAP backend seems underutilized and LDAP
> backend development has been neglected for years (due to lack of interest and
> private investment), I see much potential in it, as you, and it would be worth
> trying to revive it.
Yes, IMHO it
On 4/3/2015 8:17 μμ, Michael Ströder wrote:
This sounds a bit like a special case for split horizon DNS.
Precisely.
I promised to configure a demo using powerdns with LDAP backend for this based
on OpenLDAP ACLs and several powerdns instances using different LDAP identities.
Feel free to co
Nikolaos Milas wrote:
> On 3/3/2015 2:44 μμ, Nikolaos Milas wrote:
>
>> Ideally, we would like pdns to be configured to reply to requests *for
>> particular names* (under a specific subdomain, say internal.example.com) by
>> only providing records (if available, otherwise no results) and hide
On 3/3/2015 2:44 μμ, Nikolaos Milas wrote:
Ideally, we would like pdns to be configured to reply to requests *for
particular names* (under a specific subdomain, say
internal.example.com) by only providing records (if available,
otherwise no results) and hide A records.
This way we could
On 3/3/2015 1:48 μμ, bert hubert wrote:
I'm not entirely sure I understand your question, since AXFRs are not sent
but requested. However, I am sure that 2.9.22 can't do this.
Thanks for the reply.
You are right. I used wrong terminology; I m
On Tue, Mar 03, 2015 at 01:31:21PM +0200, Nikolaos Milas wrote:
> We are using pdns-2.9.22 with LDAP backend, using the "Simple" LDAP
> architecture.
(...)
> internal.example.com and to not send AXFRs to the other master
> servers, as specified in nSRecord attribute, for this particular
> subdomain
Hello,
We are using pdns-2.9.22 with LDAP backend, using the "Simple" LDAP
architecture.
The server is configured as authoritative for our root domain name, say
example.com, and it performs AXFRs to other servers specified in
nSRecord attribute.
We would like to configure pdns so as to NOT
10 matches
Mail list logo
