| Parent | pass | NS records at parent servers | Your NS records at the parent servers are: ns17.zoneedit.com. ns8.zoneedit.com. [These were obtained from ns2.switch.ch.] |
| warn | Glue at parent nameservers | WARNING. The parent servers (I checked withns2.switch.ch.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records That may cause some extra miliseconds in DNS. This will usually occur if your DNS servers are not in the same TLD as your domain | |
| NS | info | NS records at your nameservers | Your NS records at your nameservers are: 209.126.159.118 Does not respond At 75.125.10.187 ns8.zoneedit.com. [unknow] ns17.zoneedit.com. [unknow] |
| skip | Mismatched glue | Skip comparing the glue provided by the parent servers and that provided by your authoritative DNS servers, as root servers do not provide glue | |
| fail | No NS A records at nameservers | Error: some servers does not provide A records for nameservers At ns8.zoneedit.com. [75.125.10.187] No A record for ns8.zoneedit.com. No A record for ns17.zoneedit.com. | |
| fail | All nameservers report identical NS records | ERROR. The NS records at all your nameservers are different, check the info above for details. | |
| fail | All nameservers respond | ERROR: some nameservers does not respond ns17.zoneedit.com. [209.126.159.118] does not respond | |
| 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 2 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: Primary nameserver: ns8.zoneedit.com. Hostmaster E-mail address: soacontact.zoneedit.com. Serial #: 2013160666 Refresh: 2400 Retry: 360 Expire: 1209600 Default TTL:300 |
| pass | NS agreement on SOA Serial # | OK. All your nameservers agree that your SOA serial number is 2013160666. That means that all your nameservers are using the same data. | |
| pass | SOA MNAME Check | OK. Your SOA (Start of Authority) record states that your master (primary) name server is: ns8.zoneedit.com. That server is listed at the parent servers, which is correct. | |
| pass | SOA Serial Number | OK. Your SOA serial number is: 2013160666. 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 : 2400 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 : 360 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. | |
| pass | SOA EXPIRE value | Your SOA EXPIRE time is : 1209600 seconds. This seems normal (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 : 300 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. | |