Endless loop for guce.gouv.ci

[bortzmeyer]

The domain is quite weird. Investigation under way.

% ./pdig-dns-tool.py guce.gouv.ci
…
===================
ns=ci.hosting.nic.fr. addr=192.134.0.49, latency=6.773 ms
ns=ci.hosting.nic.fr. addr=2001:660:3006:1::1:1, latency=7.338 ms
ns=ns.nic.ci. addr=196.49.0.84, latency=103.665 ms
ns=any.nic.ci. addr=204.61.216.120, latency=5.296 ms
ns=any.nic.ci. addr=2001:500:14:6120:ad::1, latency=7.860 ms
ns=ns-ci.afrinic.net. addr=196.216.168.30, latency=188.582 ms
ns=ns-ci.afrinic.net. addr=2001:43f8:120::30, latency=182.669 ms
ns=phloem.uoregon.edu. addr=128.223.32.35, latency=148.648 ms
timeout querying: 2001:468:d01:20::80df:2023
latency: min=5.296 ms max=188.582 ms avg=81.354 ms
stdev=83.679 ms max-min=183.286 max/min=35.61 x latency variance
===================
ns=ns3.sndi.ci. addr=164.160.41.43, latency=101.381 ms
ns=ns2.sndi.ci. addr=164.160.41.42, latency=102.387 ms
ns=ns1.sndi.ci. addr=164.160.41.41, latency=101.341 ms
ns=ns4.sndi.ci. addr=77.68.50.56, latency=19.148 ms
latency: min=19.148 ms max=102.387 ms avg=81.064 ms
stdev=41.281 ms max-min=83.239 max/min=5.35 x latency variance
===================
ns=ns1.sndi.ci. addr=164.160.41.41, latency=101.199 ms
ns=ns01.guce.gouv.ci. addr=196.10.122.71, latency=101.686 ms
ns=ns2.sndi.ci. addr=164.160.41.42, latency=101.689 ms
ns=ns4.sndi.ci. addr=77.68.50.56, latency=18.812 ms
ns=ns02.guce.gouv.ci. addr=196.10.122.70, latency=103.608 ms
ns=ns03.guce.gouv.ci. addr=196.10.123.70, latency=108.035 ms
ns=ns3.sndi.ci. addr=164.160.41.43, latency=102.628 ms
latency: min=18.812 ms max=108.035 ms avg=91.094 ms
stdev=31.958 ms max-min=89.223 max/min=5.74 x latency variance
===================
ns=ns4.sndi.ci. addr=77.68.50.56, latency=19.626 ms
ns=ns01.guce.gouv.ci. addr=196.10.122.71, latency=103.156 ms
ns=ns02.guce.gouv.ci. addr=196.10.122.70, latency=97.952 ms
ns=ns03.guce.gouv.ci. addr=196.10.123.70, latency=103.676 ms
ns=ns1.sndi.ci. addr=164.160.41.41, latency=100.718 ms
ns=ns2.sndi.ci. addr=164.160.41.42, latency=101.074 ms
ns=ns3.sndi.ci. addr=164.160.41.43, latency=101.883 ms
latency: min=19.626 ms max=103.676 ms avg=89.726 ms
stdev=30.968 ms max-min=84.050 max/min=5.28 x latency variance
… (for ever)

[bortzmeyer]

This is because some servers like 164.160.41.43 do not reply with the AA flag so the servers in the authority section are used, even if they are the same as the current list.