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:

ns1.gov.az.   ['31.170.237.118']   [TTL=86400]
ns2.gov.az.   ['85.132.27.158']   [TTL=86400]
ns3.gov.az.   ['31.170.237.117']   [TTL=86400]
ns4.gov.az.   ['85.132.27.157']   [TTL=86400]

az.hostmaster.ua directed me to ns3.gov.az which was kind enough to give us that information.
NOTE: You also need to know that you have a country code second-level domain (ccSLD) that may require an extra NS lookup and may delay a little the visitors to your website!
Warn TLD Parent Check WARNING: Looks like the parent servers do not have information for your TLD when asked. This is ok but can be confusing.
Pass Your nameservers are listed Good. The parent server az.hostmaster.ua 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.
Pass DNS Parent sent Glue Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3)
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:

ns1.gov.az  ['31.170.237.118']   [TTL=86400]
ns2.gov.az  ['85.132.27.158']   [TTL=86400]
ns3.gov.az  ['31.170.237.117']   [TTL=86400]
ns4.gov.az  ['85.132.27.157']   [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.
Pass Same Glue The A records (the GLUE) got from the parent zone check are the same as 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 according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below!
Pass Glue for NS records OK. When I asked your nameservers for your NS records they also returned the A records for the NS records. This is a good thing as it will spare an extra A lookup needed to find those A records.
Pass Mismatched NS records OK. The NS records at all your nameservers are identical.
Pass DNS servers responded Good. All nameservers listed at the parent server responded.
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:
31.170.237.117
85.132.27.157
85.132.27.158
31.170.237.118
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 az.hostmaster.ua 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.railway.gov.az!

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

Processed in 0.853 seconds.