DNS report for zone “h1pp1e.net”
Hostmasters for zone h1pp1e.net is: dnsadmin@afraid.org , hostmaster@h1pp1e.netIP settings (as seen from ns4.afraid.org)
info
You have 6 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from ns4.afraid.org)
info
You have 7 mailservers.
Zone as seen from “ns1.afraid.org” [67.19.72.206]
error
ns1.afraid.org is out of sync, it's running a version of the zone with serial 905070001 when the newest one is 1241738340.
warn
We recommend that you keep your SOA in YYYYMMDDxx-format.
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 120 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.
Zone as seen from “ns1.cdmon.net” [212.36.74.129]
info
ns1.cdmon.net is running the latest version of the zone(1241738340).
warn
We recommend that you keep your SOA in YYYYMMDDxx-format.
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 604800 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 21600 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns2.afraid.org” [66.252.5.14]
error
Host is down!
Zone as seen from “ns2.cdmon.net” [212.36.75.129]
info
ns2.cdmon.net is running the latest version of the zone(1241738340).
warn
We recommend that you keep your SOA in YYYYMMDDxx-format.
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 604800 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 21600 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns3.afraid.org” [72.20.15.62]
error
ns3.afraid.org is out of sync, it's running a version of the zone with serial 905070001 when the newest one is 1241738340.
warn
We recommend that you keep your SOA in YYYYMMDDxx-format.
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.
info
Your SOA retry value of 120 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.
Zone as seen from “ns3.cdmon.net” [213.186.58.203]
info
ns3.cdmon.net is running the latest version of the zone(1241738340).
warn
We recommend that you keep your SOA in YYYYMMDDxx-format.
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 604800 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 21600 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns4.afraid.org” [208.43.71.243]
error
ns4.afraid.org is out of sync, it's running a version of the zone with serial 905070001 when the newest one is 1241738340.
warn
We recommend that you keep your SOA in YYYYMMDDxx-format.
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 120 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.