DNS report for zone “wiellyam.net”
Hostmasters for zone wiellyam.net is: root@ddns1.interlink.or.jp , root@ddns2.interlink.or.jpIP settings (as seen from ddns2.interlink.or.jp)
info
You have 2 nameservers.
info
You have nameservers in several C-Nets, that's good!
Mail settings (as seen from ddns2.interlink.or.jp)
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 “ddns1.interlink.or.jp” [203.141.128.39]
info
ddns1.interlink.or.jp is running the latest version of the zone(1).
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 240 minutes is good.
warn
A SOA retry value of 14400 is too infrequent, we propose you set this to a value inbetween 120 and 7200 seconds.
warn
A SOA expiry value of 86400 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 600 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.
Zone as seen from “ddns2.interlink.or.jp” [203.141.142.30]
info
ddns2.interlink.or.jp is running the latest version of the zone(1).
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 240 minutes is good.
warn
A SOA retry value of 14400 is too infrequent, we propose you set this to a value inbetween 120 and 7200 seconds.
warn
A SOA expiry value of 86400 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 600 is too low. RFC2308 recommends a minimum TTL between 1-3 hours.