DNS report for zone “angelsecret.net”
Hostmaster for zone angelsecret.net is: hostmaster@namesecure.comIP settings (as seen from dns2.namesecure.com)
info
You have 2 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from dns2.namesecure.com)
warn
You have only 1 mailserver. Consider getting a backup one!
Zone as seen from “dns1.namesecure.com” [205.178.190.113]
info
dns1.namesecure.com is running the latest version of the zone(2005051104).
info
SOA serial seems to follow good standards. We recommend it to be in YYYYMMDDxx-format, which yours appear to be. This would suggest that your zone was last updated at 2005-05-11, and has been updated 5 times on that day.
info
This nameserver does not allow zone transfers.
info
This nameserver does not support recursion, which is good. Public nameservers should never support recursion.
info
Your nameserver responds to queries via TCP.
info
Your nameserver responds authorative for the zone.
warn
SOA Refresh value of 172800 is too high. RFC1912 suggests it should be between 1200 and 43200 seconds. This sets how often slaves should refresh the zone from the master.
info
Your SOA retry value of 60 minutes is good.
warn
A SOA expiry value of 2592000 is quite high. You should consider lowering this to a value inbetween 2 and 4 weeks. This value defines for how long the zone should be valid when the slaves are unable to reach the master.
Zone as seen from “dns2.namesecure.com” [205.178.188.54]
info
dns2.namesecure.com is running the latest version of the zone(2005051104).
info
SOA serial seems to follow good standards. We recommend it to be in YYYYMMDDxx-format, which yours appear to be. This would suggest that your zone was last updated at 2005-05-11, and has been updated 5 times on that day.
info
This nameserver does not allow zone transfers.
info
This nameserver does not support recursion, which is good. Public nameservers should never support recursion.
info
Your nameserver responds to queries via TCP.
info
Your nameserver responds authorative for the zone.
warn
SOA Refresh value of 172800 is too high. RFC1912 suggests it should be between 1200 and 43200 seconds. This sets how often slaves should refresh the zone from the master.
info
Your SOA retry value of 60 minutes is good.
warn
A SOA expiry value of 2592000 is quite high. You should consider lowering this to a value inbetween 2 and 4 weeks. This value defines for how long the zone should be valid when the slaves are unable to reach the master.