DNS report for zone “moneylaundering101.org”
Hostmaster for zone moneylaundering101.org is: postmaster@san.yahoo.comIP settings (as seen from ns8.san.yahoo.com)
info
You have 4 nameservers.
info
You have nameservers in several C-Nets, that's good!
warn
moneylaundering101.org points to more than one IP address, are you sure this is how you want it? Addresses: 98.136.92.76 , 98.136.92.77 , 98.136.92.78
Mail settings (as seen from ns8.san.yahoo.com)
info
You have 2 mailservers.
Zone as seen from “yns2.yahoo.com” [66.196.84.168]
error
yns2.yahoo.com is out of sync, it's running a version of the zone with serial 2009102401 when the newest one is 2009121101.
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-10-24, and has been updated 2 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.
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 7084000 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 28800 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns9.san.yahoo.com” [66.196.84.168]
error
ns9.san.yahoo.com is out of sync, it's running a version of the zone with serial 2009092301 when the newest one is 2009121101.
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-09-23, and has been updated 2 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.
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 7084000 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 28800 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “yns1.yahoo.com” [98.136.43.32]
info
yns1.yahoo.com is running the latest version of the zone(2009121101).
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-12-11, and has been updated 2 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.
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 7084000 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 28800 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns8.san.yahoo.com” [98.136.43.32]
info
ns8.san.yahoo.com is running the latest version of the zone(2009121101).
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-12-11, and has been updated 2 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.
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 7084000 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 28800 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.