I have read other posts where people are mystified by the ressults of DNScog testing.
In my case, one glaring example is that DNScog claims it cannot send mail to "postmaster," yet everyone else in the world can.
Once one gets one result which is absolutely false, then one questions the reliability of the entire test.
asked Dec 30 '10 at 02:55 PM in Default
I only experience problems with these two mail related DNSCog tests:
The problem being that DNSCog believes I have duplicate MX and SPF records.
I have no problems with the postmaster@ or abuse@ tests. If you click "View Details", what does it say?
answered Dec 30 '10 at 03:06 PM
I haven't had any problems with the output and testing against my own servers everything works correctly.
Have you yet checked the logs of your mail server? I'm expecting that you've got some form of filtering going on, possibly greylisting or possibly just simple firewalling.
That suggests that they're having problems contacting your mail server, quite probably your entire system. I assume you don't normally have connectivity problems?
There are issues with DNScog which is why it says beta. Not all mail servers are configured the same.
Mine uses all available spam technologies. One of which beiong reverse dns lookups. DNScog fails with this since the ip the service runs from does not resolve to a host name therefore my mail server rejects the DNScog service for mail tests. Ironic isnt it?
I too experience duplicate addresses in dns for spf and others.
Like I said it is still beta. There are going to be issues. Reliable? That depends on how much you know about your own setup and how email works in detail to get what you need when using DNScog.
A much better service to use would be www.intodns.com
answered Jan 11 '11 at 11:36 AM