DNS report for zone “fx-onlinetrading.net”
Hostmaster for zone fx-onlinetrading.net is: hostmaster@superb.netIP settings (as seen from ns5.superb.net)
info
You have 5 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from ns5.superb.net)
warn
You have only 1 mailserver. Consider getting a backup one!
Zone as seen from “ns1.superb.net” [66.36.226.4]
info
ns1.superb.net is running the latest version of the zone(1262313903).
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 1262-03-13, and has been updated 904 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.
info
Your nameserver responds to queries via TCP.
info
Your nameserver responds authorative for the zone.
warn
SOA Refresh value of 0 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 0 is too frequent. We propose you increase this to at least 120 seconds.
warn
A SOA expiry value of 0 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 0 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns2.superb.net” [209.160.56.15]
info
ns2.superb.net is running the latest version of the zone(1262313903).
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 1262-03-13, and has been updated 904 times on that day.
warn
This nameserver supports zone transfers. This enables people to fetch a list of all DNS records in your zone. To view the list please click here!
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 0 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 0 is too frequent. We propose you increase this to at least 120 seconds.
warn
A SOA expiry value of 0 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 0 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns3.superb.net” [207.228.249.4]
info
ns3.superb.net is running the latest version of the zone(1262313903).
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 1262-03-13, and has been updated 904 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.
info
Your nameserver responds to queries via TCP.
info
Your nameserver responds authorative for the zone.
warn
SOA Refresh value of 0 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 0 is too frequent. We propose you increase this to at least 120 seconds.
warn
A SOA expiry value of 0 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 0 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns4.superb.net” [207.228.225.4]
info
ns4.superb.net is running the latest version of the zone(1262313903).
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 1262-03-13, and has been updated 904 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.
info
Your nameserver responds to queries via TCP.
info
Your nameserver responds authorative for the zone.
warn
SOA Refresh value of 0 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 0 is too frequent. We propose you increase this to at least 120 seconds.
warn
A SOA expiry value of 0 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 0 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ns5.superb.net” [209.160.56.4]
info
ns5.superb.net is running the latest version of the zone(1262313903).
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 1262-03-13, and has been updated 904 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.
info
Your nameserver responds to queries via TCP.
info
Your nameserver responds authorative for the zone.
warn
SOA Refresh value of 0 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 0 is too frequent. We propose you increase this to at least 120 seconds.
warn
A SOA expiry value of 0 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 0 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.