DNS report for zone “vnt.org”
Hostmaster for zone vnt.org is: info@vnt.orgIP settings (as seen from ns3.pem.kpn.net)
info
You have 2 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from ns3.pem.kpn.net)
info
You have 2 mailservers.
Zone as seen from “ns1.pem.kpn.net” [195.121.1.59]
info
ns1.pem.kpn.net is running the latest version of the zone(1257177004).
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.
info
Your SOA refresh value of 333 minutes is good.
warn
A SOA retry value of 20000 is too infrequent, we propose you set this to a value inbetween 120 and 7200 seconds.
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.pem.kpn.net” [213.75.76.84]
info
ns3.pem.kpn.net is running the latest version of the zone(1257177004).
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.
info
Your SOA refresh value of 333 minutes is good.
warn
A SOA retry value of 20000 is too infrequent, we propose you set this to a value inbetween 120 and 7200 seconds.
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.