pageoneresults - 6:46 pm on Jul 8, 2008 (gmt 0)

Hey, I'm guilty! Okay, so I failed to run a DNS Report on a few sites due to a "false sense of security". Yes, I too suffer the same challenges that many of us do when dealing with the alphabet soup of protocols, best practices, etc.

One of the areas that I got real lax in was "spot checking" DNS for websites that we do not control DNS for. A few years ago I went on this mission to get DNS locked down within our network so I could have a "sense of security" that if something ever were to go wrong, we couldn't blame DNS which seems to be the nemesis of many here at WebmasterWorld. And, many don't know it just yet. :(

Just yesterday, we ran a DNS report for a domain that we are launching a new application on. My programmer out of "best practice" ran the report and what did we find? Okay, you tell me, if you were in charge of DNS, what would this say to you?

NS
----------
FAIL - Open DNS Servers
WARN - All nameservers report identical NS records
FAIL - Missing nameservers 2
WARN - TCP Allowed

SOA
----------
FAIL - NS agreement on SOA Serial #

Mail
----------
WARN - Mail server host name in greeting
WARN - Acceptance of postmaster address
WARN - SPF record

Yes, I do believe email is sent from the same server network and the errors are across the board.

If you had 100+ websites under DNS which reported the above FAILs and WARNs, how would you feel?

As an Internet Marketer, the above would be a concern for me. Especially the Open DNS Server FAIL. I've been through that issue before and many brushed it off as the whole "small percentage" bit. That's fine but, does that mean that these holes should be left open for miscreants?

Some history on the Open DNS Servers challenge...

DNS Recursion - Open DNS Servers
The new open relay problem. Are you addressing this?
[webmasterworld.com...]