Vincent Levigneron

This case has always been a `WARNING`. It has not changed. Severity level of messages could be added in https://github.com/zonemaster/zonemaster/blob/master/docs/specifications/tests/Zone-TP/zone05.md like it has been done in more recents tests cases...

For those interested in that subject. These are some references: The disclosure presentation during the last OARC meeting: https://indico.dns-oarc.net/event/38/contributions/849/attachments/814/1465/tsuname-slides-oarc35.pdf The tool used to detect this specific configuration : https://github.com/SIDN/CycleHunter All...

2 domains that we used for the tests: tsuname.zut-root.rd.nic.fr. 30 IN NS ns1.tsunayou.zft-root.rd.nic.fr. tsuname.zut-root.rd.nic.fr. 30 IN NS ns2.tsunayou.zft-root.rd.nic.fr. tsunayou.zft-root.rd.nic.fr. 30 IN NS ns2.tsuname.zut-root.rd.nic.fr. tsunayou.zft-root.rd.nic.fr. 30 IN NS ns1.tsuname.zut-root.rd.nic.fr.

le 29 Jul, Mats Dufberg a ?crit : > @vlevigneron, I have failed to find a good solution on this. Can you take a look at it? > OK, but...

I see that @matsduf and I have no idea how to fix zonemaster/zonemaster-cli#160. What we see is what is expected from MooseX::Getopt. I found no way to change that behaviour...

Everything is possible but it would be a complete rewrite of zonemaster-cli/lib/Zonemaster/CLI.pm.

I guess I found something. I'll create a PR today, you'll see if it is an acceptable workaround.

Yes of course, once I'll be back from vacation. 2015-04-27 11:18 GMT+02:00 Patrik Wallström [email protected]: > @vlevigneron https://github.com/vlevigneron Is this something you can > spend some time on? > >...

Yes this is the plan. The current code must be considered as a first step of a more complex process we need to describe and put in place to keep...

nameserver03 uses AXFR, which is not cached, Cf zonemaster/zonemaster-engine#189 nameserver08 and nameserver09 use randomized case domain names, which prevent them to be cached. This randomization can be fixed if we...