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:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |