| Parent | pass | NS records at parent servers | Your NS records at the parent servers are: ns1.sqpt.net. [ 208.86.158.192 ] ns17.zoneedit.com. [ 209.126.159.118 ] ns2.zoneedit.com. [ 69.72.158.226 ] [These were obtained from g.gtld-servers.net.] |
| pass | Glue at parent nameservers | Parent nameservers (I checked with g.gtld-servers.net.) know A record for your domain, Very good ! | |
| NS | info | NS records at your nameservers | Your NS records at your nameservers are: ns1.sqpt.net. [208.86.158.192 ] ns2.zoneedit.com. [unknow] ns17.zoneedit.com. [unknow] |
| pass | Mismatched glue | OK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers. | |
| fail | No NS A records at nameservers | Error: some servers does not provide A records for nameservers At ns1.sqpt.net. [208.86.158.192] No A record for ns2.zoneedit.com. No A record for ns17.zoneedit.com. At ns17.zoneedit.com. [209.126.159.118] No A record for ns2.zoneedit.com. No A record for ns17.zoneedit.com. No A record for ns1.sqpt.net. At ns2.zoneedit.com. [69.72.158.226] No A record for ns2.zoneedit.com. No A record for ns17.zoneedit.com. No A record for ns1.sqpt.net. | |
| pass | All nameservers report identical NS records | OK. The NS records at all your nameservers are identical. | |
| pass | All nameservers respond | OK. All of your nameservers listed at the parent nameservers responded. | |
| pass | Nameserver name validity | OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names). | |
| pass | Number of nameservers | OK. You have 3 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7. | |
| pass | Lame nameservers | OK. All the nameservers listed at the parent servers answer authoritatively for your domain. | |
| pass | Missing (stealth) nameservers | OK. All 2 of your nameservers (as reported by your nameservers) are also listed at the parent servers. | |
| pass | Missing nameservers 2 | OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers. | |
| pass | Nameservers on separate class C's | Your nameservers seems to be in different networks. | |
| pass | All NS IPs public | OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays. | |
| SOA | info | SOA record | Your SOA record is: At ns1.sqpt.net.[208.86.158.192] Primary nameserver: ns1.sqpt.net. Hostmaster E-mail address: sqptdns.gmail.com. Serial #: 2010011005 Refresh: 7200 Retry: 3600 Expire: 86400 Default TTL:3600 At ns17.zoneedit.com.[209.126.159.118] Primary nameserver: ns2.zoneedit.com. Hostmaster E-mail address: soacontact.zoneedit.com. Serial #: 1263118843 Refresh: 3600 Retry: 1800 Expire: 950400 Default TTL:1800 At ns2.zoneedit.com.[69.72.158.226] Primary nameserver: ns2.zoneedit.com. Hostmaster E-mail address: soacontact.zoneedit.com. Serial #: 1263118843 Refresh: 3600 Retry: 1800 Expire: 950400 Default TTL:1800 |
| fail | NS agreement on SOA Serial # | ERROR: some nameservers have different soa serial number, that can occur because recent master update (slave have not loaded master zone yet) or probably the is a problem in DNS. | |
| pass | SOA MNAME Check | OK. Your SOA (Start of Authority) record states that your master (primary) name server is: ns1.sqpt.net. That server is listed at the parent servers, which is correct. | |
| pass | SOA Serial Number | OK. Your SOA serial number is: 2010011005. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. This number must be incremented every time you make a DNS change. | |
| pass | SOA REFRESH value | Your SOA REFRESH interval is : 7200 seconds. This seems normal (about 3600-7200 seconds is good if not using DNS NOTIFY; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours)). This value determines how often secondary/slave nameservers check with the master for updates. | |
| pass | SOA RETRY value | Your SOA RETRY interval is : 3600 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed. | |
| warn | SOA EXPIRE value | Your SOA EXPIRE time is : 86400 seconds. This seems too small (about 1209600 to 2419200 seconds (2-4 weeks) is good). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver. | |
| pass | SOA MINIMUM TTL value | Your SOA MINIMUM TTL is : 3600 seconds. This seems normal (about 3,600 to 86400 seconds or 1-24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching. | |