bind 9.11 resolving PTR record only after a few tries, +trace always, no CNAME involved?

[Tony Finch]

Steffen Breitbach via bind-users <bind-users at lists.isc.org> wrote:
>
> I am having issues with my bind server setup. When I try to resolve the PTR
> for 130.248.154.166 or 172.82.233.25, I will get the proper result only after
> a few tries so. After that, resolving will work.

Looks like there are some discrepancies with the delegations which might
be the cause of the problems:

https://dnsviz.net/d/25.233.82.172.in-addr.arpa/dnssec/

    172.in-addr.arpa to 233.82.172.in-addr.arpa: The following NS name(s)
were found in the authoritative NS RRset, but not in the delegation NS
RRset (i.e., in the 172.in-addr.arpa zone): ns-261.awsdns-32.com,
ns-653.awsdns-17.net, ns-1527.awsdns-62.org, ns-1856.awsdns-40.co.uk

    172.in-addr.arpa to 233.82.172.in-addr.arpa: The following NS name(s)
were found in the delegation NS RRset (i.e., in the 172.in-addr.arpa
zone), but not in the authoritative NS RRset: a.ns.campaign.adobe.com,
b.ns.campaign.adobe.com, c.ns.campaign.adobe.com, d.ns.campaign.adobe.com

https://dnsviz.net/d/166.154.248.130.in-addr.arpa/dnssec/

    130.in-addr.arpa to 154.248.130.in-addr.arpa: The following NS name(s)
were found in the authoritative NS RRset, but not in the delegation NS
RRset (i.e., in the 130.in-addr.arpa zone): ns-653.awsdns-17.net,
ns-261.awsdns-32.com, ns-1527.awsdns-62.org, ns-1856.awsdns-40.co.uk

    130.in-addr.arpa to 154.248.130.in-addr.arpa: The following NS name(s)
were found in the delegation NS RRset (i.e., in the 130.in-addr.arpa
zone), but not in the authoritative NS RRset: a.ns.campaign.adobe.com,
b.ns.campaign.adobe.com, c.ns.campaign.adobe.com, d.ns.campaign.adobe.com

Tony.
-- 
f.anthony.n.finch  <dot at dotat.at>  http://dotat.at/
Lands End to St Davids Head including the Bristol Channel: Variable 2 to 4.
Slight in west, smooth in east. Showers, thundery at times. Good, occasionally
poor.