WARNING
The parent servers 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 milliseconds in DNS. This will usually occur if your DNS servers are not in the same TLD as your domain
SUCCESS
Nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
Nameservers report identical NS records
7/7
SUCCESS
The NS records at all your nameservers are identical.
Nameservers respond
10/10
SUCCESS
All of your nameservers listed at the parent nameservers responded.
Nameserver name validity
7/7
SUCCESS
All of the NS records that your nameservers report are valid (no IPs or partial domain names).
Number of nameservers
2/5
WARNING
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.
Lame nameservers
7/7
SUCCESS
All the nameservers listed at the parent servers answer authoritatively for your domain.
Missing (stealth) nameservers
7/7
SUCCESS
All your nameservers are also listed at the parent servers.
Root missing nameservers
0/7
DANGER
There are nameservers not listed at your nameservers:
SUCCESS
All of your NS records appear to use public IPs.
SOA
SOA record
SOA record is:
Hostmaster email
admin.suspended-domain.com
Serial
2012022012
Refresh
7200
Retry
7200
Expire
172800
TTL
600
Serial agreement
7/7
SUCCESS
All your nameservers agree that your SOA serial number is 2012022012 That means that all your nameservers are using the same data.
SOA MNAME
0/3
DANGER
SOA (Start of Authority) record states that your master (primary) name server is: ns1.verification-hold.suspended-domain.com, but that server is not listed at the parent servers.
Serial value
1/1
SUCCESS
SOA serial number is: 2012022012 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.
Refresh value
1/1
SUCCESS
SOA Retry interval is : 7200 seconds. This seems OK. (Values 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.
Retry value
1/1
SUCCESS
SOA Retry interval is : 7200 seconds. This seems OK. (Values 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.
Expire value
0/1
WARNING
SOA Expire time is : 172800 seconds. This seems too small. (Values 604800 to 2419200 seconds (1-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.
TTL value
1/1
SUCCESS
SOA Expire time is : 600 seconds. This seems OK. (about 300 to 86400 seconds or 5 min - 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.
Info
DNS trace
Trace to natabanu.net
lookup natabanu.net at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup natabanu.net at a.gtld-servers.net(192.5.6.30) 5 ms
a.gtld-servers.net(192.5.6.30) refer to dns11.parkpage.foundationapi.com(unknow IP)
extra IP lookup for dns11.parkpage.foundationapi.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns11.parkpage.foundationapi.com at A.ROOT-SERVERS.NET(198.41.0.4) 16 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup dns11.parkpage.foundationapi.com at e.gtld-servers.net(192.12.94.30) 5 ms
e.gtld-servers.net(192.12.94.30) refer to andy.ns.cloudflare.com(108.162.193.101)
lookup dns11.parkpage.foundationapi.com at andy.ns.cloudflare.com(108.162.193.101) 4 ms
got A record 'dns11.parkpage.foundationapi.com IN A 162.215.253.182' from dns11.parkpage.foundationapi.com(108.162.193.101)
lookup natabanu.net at dns11.parkpage.foundationapi.com(162.215.253.182) 112 ms
got A record 'natabanu.net IN A 13.248.196.204' from natabanu.net(162.215.253.182)