View Single Post
  #2  
Old 8th October 2006, 15:11
falko falko is online now
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,740 Times in 2,575 Posts
Default

Quote:
Originally Posted by VMartins
1 - 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 200.188.210.54 reports that it will do recursive lookups. [test]
Server 200.188.210.54 reports that it will do recursive lookups. [test]

See this page for info on closing open DNS servers.
Have a look here: http://www.howtoforge.com/forums/sho...en+DNS+servers
http://www.howtoforge.com/forums/sho...en+DNS+servers


Quote:
Originally Posted by VMartins
2 - FAIL No NS A records at nameservers WARNING: Your nameservers do not include any corresponding A records when asked for your NS records. They probably are not returning the A records when asked, which can prevent some other DNS servers from contacting your DNS servers. They should do this if they are authoritative for those A records. The problem record(s) are:
Nameserver 200.188.210.54 did not provide IPs for all NS records.
Nameserver 200.188.210.54 did not provide IPs for all NS records.
Please check if you have NS records in the zone file.

Quote:
Originally Posted by VMartins
3 - FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server). The problem MX records are:
54.210.188.200.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)]
Please ask your ISP to create PTR records for your IP addresses.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote