DNS report for zone jrtaksi.net
Hostmaster for zone jrtaksi.net is: hostmaster@kirahvi.comIP settings (as seen from ns2.kirahvi.com)
info
You have 2 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from ns2.kirahvi.com)
info
You have 2 mailservers.
Zone as seen from ns1.kirahvi.com [79.171.232.2]
info
ns1.kirahvi.com is running the latest version of the zone(2004042106).
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 2004-04-21, and has been updated 7 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 60480 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.
warn
A SOA retry value of 8640 is too infrequent, we propose you set this to a value inbetween 120 and 7200 seconds.
warn
A SOA expiry value of 241920 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 60480 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from ns2.kirahvi.com [62.240.69.61]
info
ns2.kirahvi.com is running the latest version of the zone(2004042106).
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 2004-04-21, and has been updated 7 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 60480 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.
warn
A SOA retry value of 8640 is too infrequent, we propose you set this to a value inbetween 120 and 7200 seconds.
warn
A SOA expiry value of 241920 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 60480 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.