I would concur, dnschecker shows incorrect information. I feel that it could be their recursive dns failing to provide correct responses, or a coding error?
Either way, I wouldn't use it. When I check using "dig" all records show correctly. Using mxtoolbox.com is another option if you are not familiar with "dig" and the applicable RFCs. Adam On Mon., Jun. 14, 2021, 10:04 a.m. Dave Lawrence, <[email protected]> wrote: > Tony Finch writes: > > > So, what are people's favorite tools, especially those that you can > just > > > point a user at? > > > > I wouldn't point a user at any of these unless I think they have a good > > amount of DNS expertise :-) > > Indeed. I recently had to field a complaint that invoked an analysis > by https://dnschecker.org/domain-health-checker.php as being related > to problems someone was seeing. That report didn't show errors, but > of the eight warnings that it issued--and that the reporter thought > needed attention--they were either incorrect, irrelevant, inscrutable, > or simply wrong. > > > _______________________________________________ > dns-operations mailing list > [email protected] > https://lists.dns-oarc.net/mailman/listinfo/dns-operations >
_______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations
