Category | Status | Test name | Information send feedback |
---|---|---|---|
Parent | Domain NS records | Nameserver records returned by the parent servers are: ns2.rondpark.com. ['185.126.6.204'] (NO GLUE) [TTL=1440] ns1.rondpark.com. ['185.126.6.204'] (NO GLUE) [TTL=1440] a.nic.ir was kind enough to give us that information.
| |
TLD Parent Check | Good. a.nic.ir, 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. | ||
Your nameservers are listed | Good. The parent server a.nic.ir 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. | ||
DNS Parent sent Glue | The parent nameserver a.nic.ir 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.) | ||
Nameservers A records | Good. Every nameserver listed has A records. This is a must if you want to be found. | ||
NS | NS records from your nameservers | NS records got from your nameservers listed at the parent NS are: Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly. |
|
Recursive Queries | Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone. | ||
Same Glue | Hmm,I do not consider this to be an error yet, since I did not detect any nameservers at your nameservers. | ||
Glue for NS records | OK. Your nameservers (the ones reported by the parent server) have no ideea who your nameservers are so this will be a pass since you already have a lot of errors! | ||
Mismatched NS records | WARNING: One or more of your nameservers did not return any of your NS records. | ||
DNS servers responded | Good. All nameservers listed at the parent server responded. | ||
Name of nameservers are valid | OK. The nameservers reported by the parent send out nothing as shown above. I can't check nothing so it's a green! | ||
Multiple Nameservers | ERROR: Looks like you have less than 2 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. | ||
Nameservers are lame | OK. All the nameservers listed at the parent servers answer authoritatively for your domain. | ||
Missing nameservers reported by parent | OK. All NS records are the same at the parent and at your nameservers. | ||
Missing nameservers reported by your nameservers | You should already know that your NS records at your nameservers are missing, so here it is again:
ns2.rondpark.com. ns1.rondpark.com. |
||
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. | ||
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. | ||
Different subnets | OK. Looks like you have nameservers on different subnets! | ||
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 | ||
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. | ||
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. | ||
Stealth NS records sent | Ok. No stealth ns records are sent | ||
SOA | SOA record | The SOA record is: Primary nameserver: irapi.ir Hostmaster E-mail address: 2015082541.rondpark.com Serial #: 7200 Refresh: 3600 Retry: 1209600 Expire: 3600 1 hours Default TTL: 0 |
|
NSs have same SOA serial | OK. All your nameservers agree that your SOA serial number is 7200. | ||
SOA MNAME entry | WARNING: SOA MNAME (irapi.ir) is not listed as a primary nameserver at your parent nameserver! | ||
SOA Serial | Your SOA serial number is: 7200.
The recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision. Your SOA serial appears to be the number of seconds since midnight 01 Jan 1970 when the last DNS change was made. That seems to be 1969/12/31 20:0:0 |
||
SOA REFRESH | OK. Your SOA REFRESH interval is: 3600. That is OK | ||
SOA RETRY | Your SOA RETRY value is: 1209600. That is NOT OK | ||
SOA EXPIRE | Your SOA EXPIRE number is: 3600. That is NOT OK | ||
SOA MINIMUM TTL | Your SOA MINIMUM TTL is: 0. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a value of 1-3 hours. Your value of 0 is OK. | ||
MX | MX Records | Oh 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 | WWW A Record |
Your www.irapi.ir A record is: www.irapi.ir [185.126.6.204] |
|
IPs are public | OK. All of your WWW IPs appear to be public IPs. | ||
WWW CNAME | OK. No CNAME |
Processed in 0.918 seconds.