#Tutorials on netsimk serial number

Your SOA EXPIRE number is: 1209600.Looks ok This appears to be in the recommended format of YYYYMMDDnn. WARNING: SOA MNAME ( ) is not listed as a primary nameserver at your parent nameserver!

#Tutorials on netsimk serial number

All your nameservers agree that your SOA serial number is 2022050401. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down. It seems you are safe from a single point of failure. This is a good thing and useful even if UDP connections are used by default. Seems all your DNS servers allow TCP connections. This is a good thing because it will prevent DNS delays and other problems like Looks like the IP addresses of your nameservers are public. Looks like you have nameservers on different subnets! RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example). Missing nameservers reported by your nameserversĮRROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. You need to make sure that these nameservers are working.If they are not working ok, you may have problems! All the nameservers listed at the parent servers answer authoritatively for your domain.įAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. All of the NS records that your nameservers report seem valid. All nameservers listed at the parent server responded. The NS records at all your nameservers are identical. You can fix this for example by adding A records to your nameservers for the zones listed above. INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. If there are any missing or stealth nameservers you should see them below! This tests only nameservers that are common at the parent and at your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone. NS records got from your nameservers listed at the parent NS are: Provide 'bootstrapping' information to the nameserver.(see RFC 1912 section 2.3)

Glue records are A records that are associated with NS records to The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.

The parent server l. has your nameservers listed. This is a good thing as there are some other domain extensions like 'co.us' for example that are missing a direct check. Good. l., the parent server I interrogated, has information for your TLD. L. was kind enough to give us that information. Nameserver records returned by the parent servers are: