[dns-operations] why does that domain resolve?

Adam David adam.vallee at gmail.com
Tue Jun 15 01:42:22 UTC 2021

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.


On Mon., Jun. 14, 2021, 10:04 a.m. Dave Lawrence, <tale at dd.org> 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
> dns-operations at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20210614/a0596867/attachment.html>

More information about the dns-operations mailing list