[ldns-users] ldns-compare-zones: difference not showing up for some 'duplicate' PTRs

[Kier Prior-Williams]

Hello,

Using ldns-compare-zones, it's not showing up a difference and I can't work out why - hoping you can put me out of my misery !

ldns-compare-zones version: 1.7.1

Here's an example of the source/target zones, which I've attempted to anonymise (yes, multiple PTRs, but we are where we are!)

src/66.57.10.in-addr.arpa:
66.57.10.in-addr.arpa. 28800 IN SOA nsh1.source.com. hostmaster.source.com. 2005100530 10800 3600 2419200 900
66.57.10.in-addr.arpa. 28800 IN NS nsh1.source.com.
66.57.10.in-addr.arpa. 28800 IN NS nsp2.source.com.
66.57.10.in-addr.arpa. 28800 IN NS nsp1.source.com.
10.66.57.10.in-addr.arpa. 28800 IN PTR www.abcdef.com.
10.66.57.10.in-addr.arpa. 28800 IN PTR documentation.abcdef.com.
19.66.57.10.in-addr.arpa. 28800 IN PTR iceabc.com.
19.66.57.10.in-addr.arpa. 28800 IN PTR iceabcs.com.
19.66.57.10.in-addr.arpa. 28800 IN PTR abclink.com.

tgt/66.57.10.in-addr.arpa:
66.57.10.in-addr.arpa. 28800 IN SOA ns1.target.com. hostmaster.source.com. 2005100549 10800 3600 2419200 900
66.57.10.in-addr.arpa. 28800 IN NS ns3.target.com.
66.57.10.in-addr.arpa. 28800 IN NS ns2.target.com.
66.57.10.in-addr.arpa. 28800 IN NS ns1.target.com.
10.66.57.10.in-addr.arpa. 28800 IN PTR www.abcdef.com.
19.66.57.10.in-addr.arpa. 28800 IN PTR iceabc.com.
19.66.57.10.in-addr.arpa. 28800 IN PTR abclink.com.

Run the cmd to compare and show all differences:
# ldns-compare-zones -a prec/66.57.10.in-addr.arpa postc/66.57.10.in-addr.arpa
~+66.57.10.in-addr.arpa. 28800 IN NS ns1.target.com.
~+66.57.10.in-addr.arpa. 28800 IN NS ns2.target.com.
~+66.57.10.in-addr.arpa. 28800 IN NS ns3.target.com.
~-66.57.10.in-addr.arpa. 28800 IN NS nsh1.source.com.
~-66.57.10.in-addr.arpa. 28800 IN NS nsp1.source.com.
~-66.57.10.in-addr.arpa. 28800 IN NS nsp2.source.com.
~-19.66.57.10.in-addr.arpa. 28800 IN PTR iceabcs.com.
 +0 -0 ~2

It doesn't list the difference for the 'documentation.abcdef.com' PTR record.
It does list the difference for the next PTR (3 in the source, 2 in the target)

If I add another PTR record into both source & target, i.e.
10.66.57.10.in-addr.arpa. 28800 IN PTR documentation2.abcdef.com.

The "missing' target PTR does then show up !
# ldns-compare-zones -a prec/66.57.10.in-addr.arpa postc/66.57.10.in-addr.arpa
~+66.57.10.in-addr.arpa. 28800 IN NS ns1.target.com.
~+66.57.10.in-addr.arpa. 28800 IN NS ns2.target.com.
~+66.57.10.in-addr.arpa. 28800 IN NS ns3.target.com.
~-66.57.10.in-addr.arpa. 28800 IN NS nsh1.source.com.
~-66.57.10.in-addr.arpa. 28800 IN NS nsp1.source.com.
~-66.57.10.in-addr.arpa. 28800 IN NS nsp2.source.com.
~-10.66.57.10.in-addr.arpa. 28800 IN PTR documentation.abcdef.com.
~-19.66.57.10.in-addr.arpa. 28800 IN PTR iceabcs.com.
 +0 -0 ~3

What am I missing here ?!
Thanks.

-- 
 Kier PW

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/ldns-users/attachments/20190905/bf83299d/attachment.htm>