DNS report for zone “borderscars.net”
Hostmasters for zone borderscars.net is: administrator@borderscars.net ,IP settings (as seen from ns3.livedns.co.uk)
info
You have 3 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from ns3.livedns.co.uk)
warn
You don't have any mailservers set up. This is OK if you don't use any mail for the domain.
Zone as seen from “ns1.livedns.co.uk” [213.171.192.250]
info
ns1.livedns.co.uk is running the latest version of the zone(200912119).
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-12-11, and has been updated 10 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.
warn
Your nameserver doesn't respond 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 86400 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns2.livedns.co.uk” [213.171.193.250]
error
ns2.livedns.co.uk is out of sync, it's running a version of the zone with serial when the newest one is 200912119.
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 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 is too frequent. We propose you increase this to at least 120 seconds.
warn
A SOA expiry value of 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 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns3.livedns.co.uk” [213.171.192.254]
error
ns3.livedns.co.uk is out of sync, it's running a version of the zone with serial when the newest one is 200912119.
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 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 is too frequent. We propose you increase this to at least 120 seconds.
warn
A SOA expiry value of 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 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.