Work in progress!

Follow IntoDNS on Twitter


Category Status Test name Information
Parent Info Domain NS records Nameserver records returned by the parent servers are:

golomb.nic.pr.   ['134.202.6.100']   [TTL=86400]
pascal.nic.pr.   ['134.202.0.120']   [TTL=86400]
descartes.nic.pr.   ['134.202.2.120']   [TTL=86400]
pr-dns.denic.de.   ['194.0.11.111'] (NO GLUE)   [TTL=86400]
pr-ns.anycast.pch.net.   ['204.61.216.23'] (NO GLUE)   [TTL=86400]

d0.pr.afilias-nst.org was kind enough to give us that information.

Pass TLD Parent Check Good. d0.pr.afilias-nst.org, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check.
Pass Your nameservers are listed Good. The parent server d0.pr.afilias-nst.org has your nameservers listed. 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.
Info DNS Parent sent Glue The parent nameserver d0.pr.afilias-nst.org 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. 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. This happens a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.)
Pass Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.
NS Info NS records from your nameserversNS records got from your nameservers listed at the parent NS are:

descartes.nic.pr  ['134.202.1.120', '134.202.2.120']   [TTL=86400]
golomb.nic.pr  ['134.202.6.100']   [TTL=86400]
pascal.nic.pr  ['134.202.0.120']   [TTL=86400]
pr-dns.denic.de  ['194.0.11.111']   [TTL=86400]
pr-ns.anycast.pch.net  ['204.61.216.23']   [TTL=86400]

Pass Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Warn Same Glue Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.I detected some problems as follows:
For descartes.nic.pr the parent reported: ['204.61.216.23'] and your nameservers reported: ['134.202.1.120', '134.202.2.120']
For golomb.nic.pr the parent reported: ['204.61.216.23'] and your nameservers reported: ['134.202.6.100']
For pascal.nic.pr the parent reported: ['204.61.216.23'] and your nameservers reported: ['134.202.0.120']
For pr-dns.denic.de the parent reported: ['204.61.216.23'] and your nameservers reported: ['194.0.11.111']
For pr-ns.anycast.pch.net the parent reported: ['204.61.216.23'] and your nameservers reported: ['204.61.216.23']
Information Glue for NS records 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. The nameservers without glue are:
194.0.11.111
You can fix this for example by adding A records to your nameservers for the zones listed above.
Pass Mismatched NS records OK. The NS records at all your nameservers are identical.
Error DNS servers responded ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
134.202.0.120 134.202.6.100 134.202.2.120 204.61.216.23
Pass Name of nameservers are valid OK. All of the NS records that your nameservers report seem valid.
Pass Multiple Nameservers Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
Error Nameservers are lame ERROR: looks like you have lame nameservers. The following nameservers are lame:
194.0.11.111
Pass Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers.
Pass Missing nameservers reported by your nameservers OK. All nameservers returned by the parent server d0.pr.afilias-nst.org are the same as the ones reported by your nameservers.
Pass Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Pass NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Pass Different subnets OK. Looks like you have nameservers on different subnets!
Pass IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
Pass DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
Pass Different autonomous systems OK. It seems you are safe from a single point of failure. 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.
Pass Stealth NS records sent Ok. No stealth ns records are sent
SOA Error SOA recordNo valid SOA record came back!
MX Error MX RecordsOh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!
WWW Error WWW A Record ERROR: I could not get any A records for www.www.pr!

(I only do a cache request, if you recently added a WWW A record, it might not show up here.)

Processed in 17.702 seconds.