DNS report for zone “splcargo.net”
Hostmasters for zone splcargo.net is: support@eazysmart.com , support@name.comIP settings (as seen from ns4.name.com)
info
You have 5 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from ns4.name.com)
warn
You have only 1 mailserver. Consider getting a backup one!
Zone as seen from “ns1.mtsuperweb.net” [202.69.111.35]
info
ns1.mtsuperweb.net is running the latest version of the zone(2009032601).
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 2009-03-26, and has been updated 2 times on that day.
warn
This nameserver supports zone transfers. This enables people to fetch a list of all DNS records in your zone. To view the list please click here!
error
Your nameserver supports recursion. This is really bad to have activated on public nameservers since they can then be used for amplification of Denial Of Service attacks! You can find more information about it here: http://www.us-cert.gov/reading_room/DNS-recursion033006.pdf
info
Your nameserver responds to queries via TCP.
info
Your nameserver responds authorative for the zone.
warn
SOA Refresh value of 86400 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 120 minutes is good.
warn
A SOA expiry value of 3600000 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.
warn
A minimum TTL (Time To Live) of 86400 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns1.name.com” [174.143.93.179]
error
ns1.name.com is out of sync, it's running a version of the zone with serial 1 when the newest one is 2009032601.
warn
We recommend that you keep your SOA in YYYYMMDDxx-format.
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.
info
Your SOA refresh value of 60 minutes is good.
info
Your SOA retry value of 60 minutes is good.
warn
A SOA expiry value of 604800 is too low. This value denotes for how long the zone is valid when the master is down. RFC1912 suggests it should be between 2 and 4 weeks.
Zone as seen from “ns2.name.com” [38.97.225.248]
error
ns2.name.com is out of sync, it's running a version of the zone with serial 1 when the newest one is 2009032601.
warn
We recommend that you keep your SOA in YYYYMMDDxx-format.
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.
info
Your SOA refresh value of 60 minutes is good.
info
Your SOA retry value of 60 minutes is good.
warn
A SOA expiry value of 604800 is too low. This value denotes for how long the zone is valid when the master is down. RFC1912 suggests it should be between 2 and 4 weeks.
Zone as seen from “ns3.name.com” [174.36.196.243]
error
ns3.name.com is out of sync, it's running a version of the zone with serial 1 when the newest one is 2009032601.
warn
We recommend that you keep your SOA in YYYYMMDDxx-format.
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.
info
Your SOA refresh value of 60 minutes is good.
info
Your SOA retry value of 60 minutes is good.
warn
A SOA expiry value of 604800 is too low. This value denotes for how long the zone is valid when the master is down. RFC1912 suggests it should be between 2 and 4 weeks.
Zone as seen from “ns4.name.com” [174.129.224.234] [174.129.224.165]
error
ns4.name.com is out of sync, it's running a version of the zone with serial 1 when the newest one is 2009032601.
warn
We recommend that you keep your SOA in YYYYMMDDxx-format.
info
This nameserver does not allow zone transfers.
info
This nameserver does not support recursion, which is good. Public nameservers should never support recursion.
warn
Your nameserver doesn't respond to queries via TCP.
info
Your nameserver responds authorative for the zone.
info
Your SOA refresh value of 60 minutes is good.
info
Your SOA retry value of 60 minutes is good.
warn
A SOA expiry value of 604800 is too low. This value denotes for how long the zone is valid when the master is down. RFC1912 suggests it should be between 2 and 4 weeks.