DNS report for zone “rubinart.ca”
Hostmaster for zone rubinart.ca is: admin@carrierzone.comIP settings (as seen from ns3.carrierzone.com)
info
You have 4 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from ns3.carrierzone.com)
info
You have 4 mailservers.
Zone as seen from “ns4.carrierzone.com” [69.49.105.100]
info
ns4.carrierzone.com is running the latest version of the zone(1006).
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 86403 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 60 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.
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 “ns1.carrierzone.com” [64.29.144.67]
info
ns1.carrierzone.com is running the latest version of the zone(1006).
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 86403 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 60 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.
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.carrierzone.com” [64.29.154.67]
info
ns2.carrierzone.com is running the latest version of the zone(1006).
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 86403 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 60 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.
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 “ns3.carrierzone.com” [216.251.32.106]
info
ns3.carrierzone.com is running the latest version of the zone(1006).
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 86403 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 60 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.
warn
A minimum TTL (Time To Live) of 86400 is quite high. RFC2308 recommends a minimum TTL between 1-3 hours.