DNS report for zone “mbngolftimes.net

Hostmaster for zone mbngolftimes.net is:   dns@ifg.net

IP settings (as seen from dns3.ifg.net)

info
You have 3 nameservers.
info
You have nameservers in several C-Nets, that's good!

Mail settings (as seen from dns3.ifg.net)

warn
You have only 1 mailserver. Consider getting a backup one!

Zone as seen from “dns1.ifg.net[66.153.206.100]  

info
dns1.ifg.net is running the latest version of the zone(2009081301).
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-08-13, 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!
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 300 is too low. RFC1912 suggests it should be between 1200 and 43200 seconds. This sets how often slaves should refresh the zone from the master.
warn
A SOA retry value of 60 is too frequent. We propose you increase this to at least 120 seconds.
warn
A SOA expiry value of 43200 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.
warn
A minimum TTL (Time To Live) of 720 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.

Zone as seen from “dns2.ifg.net[66.153.206.98]  

info
dns2.ifg.net is running the latest version of the zone(2009081301).
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-08-13, 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!
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 300 is too low. RFC1912 suggests it should be between 1200 and 43200 seconds. This sets how often slaves should refresh the zone from the master.
warn
A SOA retry value of 60 is too frequent. We propose you increase this to at least 120 seconds.
warn
A SOA expiry value of 43200 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.
warn
A minimum TTL (Time To Live) of 720 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.

Zone as seen from “dns3.ifg.net[66.153.206.99]  

info
dns3.ifg.net is running the latest version of the zone(2009081301).
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-08-13, 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!
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 300 is too low. RFC1912 suggests it should be between 1200 and 43200 seconds. This sets how often slaves should refresh the zone from the master.
warn
A SOA retry value of 60 is too frequent. We propose you increase this to at least 120 seconds.
warn
A SOA expiry value of 43200 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.
warn
A minimum TTL (Time To Live) of 720 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.

Example domain information pages

Example DNS reports