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. This is a good thing as it will spare an extra A lookup needed to find those A records. When I asked your nameservers for your NS records they also returned the A records for the 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. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. It may be that I am wrong but the chances of that are low. I could use the nameservers listed below to performe recursive queries. NS records got from your nameservers listed at the parent NS are: This happens a lot if you have nameservers on different TLD ( for example with nameserver ns.) It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. The parent nameserver c.mx-ns.mx is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those 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 c.mx-ns.mx 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. c.mx-ns.mx, the parent server I interrogated, has information for your TLD.
(NO GLUE)Ĭ.mx-ns.mx was kind enough to give us that information. OrgId: CLOUD14 Address: 101 Townsend Street City: San Francisco StateProv: CA PostalCode: 94107 Country: US RegDate: Updated: Comment: All Cloudflare abuse reporting can be done via Ref: OrgTechHandle: ADMIN2521-ARIN OrgTechName: Admin OrgTechPhone: +1-65 OrgTechEmail: OrgTechRef: OrgAbuseHandle: ABUSE2916-ARIN OrgAbuseName: Abuse OrgAbusePhone: +1-65 OrgAbuseEmail: OrgAbuseRef: OrgNOCHandle: NOC11962-ARIN OrgNOCName: NOC OrgNOCPhone: +1-65 OrgNOCEmail: OrgNOCRef: RNOCHandle: NOC11962-ARIN RNOCName: NOC RNOCPhone: +1-65 RNOCEmail: RNOCRef: RTechHandle: ADMIN2521-ARIN RTechName: Admin RTechPhone: +1-65 RTechEmail: RTechRef: RAbuseHandle: ABUSE2916-ARIN RAbuseName: Abuse RAbusePhone: +1-65 RAbuseEmail: RAbuseRef: # ARIN WHOIS data and services are subject to the Terms of Use # available at: # If you see inaccuracies in the results, please report at # Copyright 1997-2018, American Registry for Internet Numbers, Ltd.Nameserver records returned by the parent servers are:
# ASNumber: 13335 ASName: CLOUDFLARENET ASHandle: AS13335 RegDate: Updated: Comment: All Cloudflare abuse reporting can be done via Ref: OrgName: Cloudflare, Inc. # ARIN WHOIS data and services are subject to the Terms of Use # available at: # If you see inaccuracies in the results, please report at # Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
0 kommentar(er)
