This article discusses the importance of reporting issues, even if you aren't an expert, but your sixth sense tells you that something is wrong.
In my DNSSEC deployment tests, I made sure that everything was done perfectly by educating myself on the best practices and troubleshooting for correct deployment.
I mainly used two tools for dnssec verification, DNS Viz and Verisign Tool.
Only one of the two tools gave warnings, the implementation was correct and functional, but I prefer to evaluate the warnings and better understand why they are there and what they are caused by.
Now I'm no expert on nameserver configurations, but it was clear that the problems were in the root nameservers and TLD nameservers, so not in my reach.
Warnings are due to delegation misconfigurations of some name servers, I learned more about it on nslookup, a service that i use a lot for DNS troubleshooting.
So now I know a bit more about these warnings, I know it's due to TLD and root name server configurations, but I'm not an expert, I'm relatively new to this area.
So what do you do, ignore them or report them?
Personally, I don't like warnings, so I decided to contact my TLD and report these warnings.
At first they told me that it was due to my configurations on my nameservers, but I did my research and found that these warnings were present on all TLD websites.
I chose this TLD because it is managed by my registrar, Aruba, so I knew that if I reported that their TLD site was affected by these errors, they would take my request more seriously.
In fact, they passed the request on to the engineers, who were immediately at work on the problem.
So report it, and if you did your research, have faith in it.
That is why I think it is important, even if our knowledge is not great, to try to report, this process also leads us to learn more and to inform ourselves.
I would like to thank the staff at Aruba for their speed and preparation, this is not the only problem I have had and they have been very helpful.