DNS report for zone “codemeta.org”
Hostmaster for zone codemeta.org is: jbd@codemeta.comIP settings (as seen from river.codemeta.com)
info
You have 2 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from river.codemeta.com)
warn
You don't have any mailservers set up. This is OK if you don't use any mail for the domain.
Zone as seen from “rogue.codemeta.com” [199.125.75.14]
info
rogue.codemeta.com is running the latest version of the zone(2006050400).
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 2006-05-04, and has been updated 1 time 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 30 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 604800 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “linux.codemeta.com” [199.125.76.10]
error
Host is down!
Zone as seen from “river.codemeta.com” [199.125.75.9]
info
river.codemeta.com is running the latest version of the zone(2006050400).
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 2006-05-04, and has been updated 1 time 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 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 30 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 604800 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.