Moderator: Integra Moderator
FAIL Open DNS servers ERROR: One or more of your nameservers reports that it is an open DNS server. This usually means that anyone in the world can query it for domains it is not authoritative for (it is possible that the DNS server advertises that it does recursive lookups when it does not, but that shouldn't happen). This can cause an excessive load on your DNS server. Also, it is strongly discouraged to have a DNS server be both authoritative for your domain and be recursive (even if it is not open), due to the potential for cache poisoning (with no recursion, there is no cache, and it is impossible to poison it). Also, the bad guys could use your DNS server as part of an attack, by forging their IP address. Problem record(s) are:
Server 66.225.246.241 reports that it will do recursive lookups. [test] See this page for info on closing open DNS servers.
FAIL Mismatched glue ERROR: Your nameservers report glue that is different from what the parent servers report. This will cause DNS servers to get confused; some may go to the IP provided by the parent servers, while others may get to the ones provided by your authoritative DNS servers. Problem record(s) are:
ns2.gcomfx.com.:
Parent server (a.gtld-servers.net) says A record is 66.225.246.241, but
authoritative DNS server (66.225.246.240) says it is 205.234.132.158
ns1.gcomfx.com.:
Parent server (a.gtld-servers.net) says A record is 66.225.246.240, but
authoritative DNS server (66.225.246.240) says it is 66.225.219.6
ns1.gcomfx.com.:
Parent server (a.gtld-servers.net) says A record is 66.225.246.240, but
authoritative DNS server (66.225.246.241) says it is 66.225.219.6
ns2.gcomfx.com.:
Parent server (a.gtld-servers.net) says A record is 66.225.246.241, but
authoritative DNS server (66.225.246.241) says it is 205.234.132.158
Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004).
Registered users: App360MonitorBot, Bing [Bot], Google [Bot]