I think I've gotten to the bottom of this and fortunately it was
misunderstanding on my part rather than an error in either piece of
software. I incorrectly thought the local bind masters were serving up
the DS record from within the child zone when queried, but they were
of course serving up the records from the parent zone. Had I been
delegating the child zone to a different physical server, this would
have been more obvious to me.
I was expecting the external slave to serve up DS records for my
signed zone, but it doesn't because the zone does not contain the DS
records for itself and so they are not transferred via AXFR; and
because the external was not authoritative for the parent zone so
didn't return them from there either. Not being a recursive resolve, I
now realise the external slave will never respond with any DS records
for this zone.
Finally, in my example zone with child delegation, the DS records for
the delegated zone ARE correctly included in the AXFR of the parent
and I was mistaken in thinking they were not. I am not yet replicating
these to the external slave so was basing my understanding of what was
happening based on the AXFR results alone. Had I been able to
replicate these to the slave, I would have spotted my mistake when
getting back DS records from the parent zone.
Thanks for your time and apologies for my confusion!
On 10 February 2017 at 06:51, Martin Basti <mba...@redhat.com> wrote:
> I'm not sure how your DNS data are structured, but usually (properly) DS
> record is located in parent zone, so AXFR for subdomain.exmale.com should not
> return DS record, but AXFR for example.com should return DS record of
> ----- Original Message -----
> From: "Ben Roberts" <m...@benroberts.net>
> To: "Tomas Krizek" <tkri...@redhat.com>
> Cc: firstname.lastname@example.org
> Sent: Thursday, February 9, 2017 10:53:38 AM
> Subject: Re: [Freeipa-users] bind-dyndb-ldap, AXFR and DS records
> Hi Tomas,
>> when I add a DS record to LDAP (without any DNSSEC configuration),
>> it is included in my AXFR transfer. I'm using bind-dyndb-ldap-10.1.
>> I suppose you have DNSSEC configured. Could you be affected by the
>> limitations mentioned in ?
> Yes, dnssec is otherwise fully configured (the only bit I don't yet
> have is the DS records for the "example.local" parent domain
> registered upstream, but that shouldn't have any impact here. I don't
> think the linked limitations apply, I'm not attempting to use the CDS
> or CDNSKEY record types, and am manually specifying the DS records for
> the child zone.
> This is with bind 9.11 and bind-dyndb-ldap 11.0.
> Ben Roberts
> Manage your subscription for the Freeipa-users mailing list:
> Go to http://freeipa.org for more info on the project
Manage your subscription for the Freeipa-users mailing list:
Go to http://freeipa.org for more info on the project