[ldns-users] ldns_zone_sort does not always retains same order

[Wouter Wijngaards]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Ondřej,

Are you using 1.2.1, I saw in the Changelog that:
03 Oct 2007 1.2.1:
	* Fixed an offset error in rr comparison

And that could fix the trouble you have.

Best regards,
   Wouter

Ondřej Surý wrote:
> Hi,
> 
> I am trying to write zone comparator which will count additions,
> deletions and changes between two zone file.
> 
> I am sorting both zones and then uses simple iterator to walk in all
> domain records.
> 
> I have found that there is implementation error in ldns_zone_sort.  It
> doesn't retain same order in two different files:
> 
> $ ldns-read-zone -z cz.1192527904 > cza
> $ ldns-read-zone -z cz.1192531505 > czb
> $ diff -w -U 3 cza czb
> --- cza 2007-10-16 15:39:38.392629273 +0200
> +++ czb 2007-10-16 15:40:10.392819897 +0200
> @@ -14885,14 +14885,14 @@
>  adao.cz.       18000   IN      NS      ns.forpsi.net.
>  adap.cz.       18000   IN      NS      ns.adap.cz.
>  adap.cz.       18000   IN      NS      ns2.vshosting.cz.
> -adapo.cz.      18000   IN      NS      ns.forpsi.us.
> -adapo.cz.      18000   IN      NS      ns.forpsi.net.
>  ns.adap.cz.    18000   IN      A       89.235.62.134
>  adap-plus.cz.  18000   IN      NS      ns.banan.cz.
>  adap-plus.cz.  18000   IN      NS      ns2.banan.cz.
>  adap-plus.cz.  18000   IN      NS      ns3.banan.it.
>  adapo.cz.      18000   IN      NS      ns.forpsi.cn.
>  adapo.cz.      18000   IN      NS      ns.forpsi.cz.
> +adapo.cz.      18000   IN      NS      ns.forpsi.us.
> +adapo.cz.      18000   IN      NS      ns.forpsi.net.
>  adapobrno.cz.  18000   IN      NS      ns.dns4.cz.
>  adapobrno.cz.  18000   IN      NS      ns.dns4.net.
>  adapocz.cz.    18000   IN      NS      ns.dns4.cz.
> [...and more...]
> 
> I'll try to find where the error is... and report back.
> 
> Ondrej.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHFMu3kDLqNwOhpPgRAtjYAJ4mFy2tPBA8lklZCGmoloWcFDP3XgCcDJFd
u6+Wfe9qvJ3iYgR41vbr6cE=
=0cD0
-----END PGP SIGNATURE-----