DNS report for zone “pointlessnoise.net”
Hostmaster for zone pointlessnoise.net is: dnsadmin@afraid.orgIP settings (as seen from ns4.afraid.org)
info
You have 4 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from ns4.afraid.org)
warn
You have only 1 mailserver. Consider getting a backup one!
Zone as seen from “ns1.afraid.org” [67.19.72.206]
info
ns1.afraid.org is running the latest version of the zone(812210001).
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 “ns2.afraid.org” [66.252.5.14]
info
ns2.afraid.org is running the latest version of the zone(812210001).
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 “ns3.afraid.org” [72.20.15.62]
info
ns3.afraid.org is running the latest version of the zone(812210001).
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 “ns4.afraid.org” [208.43.71.243]
info
ns4.afraid.org is running the latest version of the zone(812210001).
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.