DNS report for zone “fkp.no”

Hostmaster for zone fkp.no is:   dnssupport@verisign-grs.com

IP settings (as seen from j4.nstld.com)

info
You have 7 nameservers.
info
You have nameservers in several C-Nets, that's good!

Mail settings (as seen from j4.nstld.com)

info
You have 2 mailservers.

Zone as seen from “a4.nstld.com” [192.5.6.33]  

info
a4.nstld.com is running the latest version of the zone(2017032169).
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 2017-03-21, and has been updated 70 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.
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 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 300 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.

Zone as seen from “f4.nstld.com” [192.35.51.33]  

info
f4.nstld.com is running the latest version of the zone(2017032169).
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 2017-03-21, and has been updated 70 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.
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 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 300 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.

Zone as seen from “k4.nstld.com” [192.52.178.33]  

info
k4.nstld.com is running the latest version of the zone(2017032169).
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 2017-03-21, and has been updated 70 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.
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 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 300 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.

Zone as seen from “h4.nstld.com” [192.54.112.33]  

info
h4.nstld.com is running the latest version of the zone(2017032169).
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 2017-03-21, and has been updated 70 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.
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 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 300 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.

Zone as seen from “l4.nstld.com” [192.41.162.33]  

info
l4.nstld.com is running the latest version of the zone(2017032169).
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 2017-03-21, and has been updated 70 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.
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 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 300 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.

Zone as seen from “g4.nstld.com” [192.42.93.33]  

info
g4.nstld.com is running the latest version of the zone(2017032169).
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 2017-03-21, and has been updated 70 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.
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 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 300 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.

Zone as seen from “j4.nstld.com” [192.48.79.33]  

info
j4.nstld.com is running the latest version of the zone(2017032169).
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 2017-03-21, and has been updated 70 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.
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 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 300 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.

Example domain information pages

Example DNS reports