DNS report for zone “hardwaredirect.de”
Hostmaster for zone hardwaredirect.de is: hostmaster@mivitec.netIP settings (as seen from dns2.mirsky.de)
info
You have 2 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from dns2.mirsky.de)
warn
You have only 1 mailserver. Consider getting a backup one!
Zone as seen from “dns1.mirsky.de” [89.31.4.17]
info
dns1.mirsky.de is running the latest version of the zone(2008103100).
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 2008-10-31, 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.
warn
Your nameserver doesn't respond 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.
warn
A SOA retry value of 14400 is too infrequent, we propose you set this to a value inbetween 120 and 7200 seconds.
info
Your SOA expiry value of 28 days is good.
warn
A minimum TTL (Time To Live) of 345600 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “dns2.mirsky.de” [91.90.144.53]
info
dns2.mirsky.de is running the latest version of the zone(2008103100).
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 2008-10-31, 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.
warn
Your nameserver doesn't respond 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.
warn
A SOA retry value of 14400 is too infrequent, we propose you set this to a value inbetween 120 and 7200 seconds.
info
Your SOA expiry value of 28 days is good.
warn
A minimum TTL (Time To Live) of 345600 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.