com DNS Report

Health Score: 62%

Need help fixing DNS ? Get an expert advise at support forum

Checked: 22 hours before

Parent

NS records at parent servers

e.gtld-servers.net [ 192.12.94.30 ]
b.gtld-servers.net [ 192.33.14.30 ]
j.gtld-servers.net [ 192.48.79.30 ]
m.gtld-servers.net [ 192.55.83.30 ]
i.gtld-servers.net [ 192.43.172.30 ]
f.gtld-servers.net [ 192.35.51.30 ]
a.gtld-servers.net
g.gtld-servers.net
h.gtld-servers.net
l.gtld-servers.net
k.gtld-servers.net
c.gtld-servers.net
d.gtld-servers.net
[These were obtained from a.root-servers.net]

Glue at parent nameservers 0/7

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

NS

Mismatched glue 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(b.gtld-servers.net.	172800	IN	A	192.33.14.30) present at Parent, missing at (192.5.6.30, 192.42.93.30, 192.41.162.30, 192.52.178.30, 192.26.92.30)
(j.gtld-servers.net.	172800	IN	A	192.48.79.30) present at Parent, missing at (192.5.6.30, 192.54.112.30, 192.41.162.30, 192.52.178.30)
(m.gtld-servers.net.	172800	IN	A	192.55.83.30) present at Parent, missing at (192.5.6.30, 192.42.93.30)
(i.gtld-servers.net.	172800	IN	A	192.43.172.30) present at Parent, missing at (192.5.6.30, 192.42.93.30, 192.52.178.30, 192.26.92.30, 192.31.80.30)
(f.gtld-servers.net.	172800	IN	A	192.35.51.30) present at Parent, missing at (192.5.6.30, 192.41.162.30, 192.31.80.30)
(e.gtld-servers.net.	172800	IN	A	192.12.94.30) present at Parent, missing at (192.54.112.30, 192.41.162.30, 192.26.92.30)
(k.gtld-servers.net.	172800	IN	A	192.52.178.30) present at (192.5.6.30, 192.42.93.30, 192.54.112.30, 192.41.162.30, 192.26.92.30), missing at Parent
(d.gtld-servers.net.	172800	IN	A	192.31.80.30) present at (192.5.6.30, 192.42.93.30, 192.54.112.30), missing at Parent
(a.gtld-servers.net.	172800	IN	A	192.5.6.30) present at (192.5.6.30, 192.42.93.30, 192.41.162.30, 192.52.178.30), missing at Parent
(g.gtld-servers.net.	172800	IN	A	192.42.93.30) present at (192.5.6.30, 192.41.162.30, 192.26.92.30, 192.31.80.30), missing at Parent
(h.gtld-servers.net.	172800	IN	A	192.54.112.30) present at (192.5.6.30, 192.41.162.30, 192.26.92.30), missing at Parent
(c.gtld-servers.net.	172800	IN	A	192.26.92.30) present at (192.52.178.30), missing at Parent
(l.gtld-servers.net.	172800	IN	A	192.41.162.30) present at (192.52.178.30, 192.31.80.30), missing at Parent

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (j.gtld-servers.net,b.gtld-servers.net,f.gtld-servers.net,m.gtld-servers.net,i.gtld-servers.net,c.gtld-servers.net,l.gtld-servers.net) at nameserver 192.5.6.30
missing A record(s) for (b.gtld-servers.net,i.gtld-servers.net,c.gtld-servers.net,l.gtld-servers.net,h.gtld-servers.net,g.gtld-servers.net,m.gtld-servers.net) at nameserver 192.42.93.30
missing A record(s) for (g.gtld-servers.net,a.gtld-servers.net,e.gtld-servers.net,l.gtld-servers.net,h.gtld-servers.net,c.gtld-servers.net,j.gtld-servers.net) at nameserver 192.54.112.30
missing A record(s) for (b.gtld-servers.net,e.gtld-servers.net,l.gtld-servers.net,f.gtld-servers.net,j.gtld-servers.net,c.gtld-servers.net,d.gtld-servers.net) at nameserver 192.41.162.30
missing A record(s) for (j.gtld-servers.net,g.gtld-servers.net,h.gtld-servers.net,d.gtld-servers.net,b.gtld-servers.net,i.gtld-servers.net,k.gtld-servers.net) at nameserver 192.52.178.30
missing A record(s) for (l.gtld-servers.net,c.gtld-servers.net,e.gtld-servers.net,i.gtld-servers.net,d.gtld-servers.net,b.gtld-servers.net,a.gtld-servers.net) at nameserver 192.26.92.30
missing A record(s) for (i.gtld-servers.net,c.gtld-servers.net,a.gtld-servers.net,h.gtld-servers.net,d.gtld-servers.net,f.gtld-servers.net,k.gtld-servers.net) at nameserver 192.31.80.30

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

Nameservers respond 0/10

Some nameservers does not respond:
2001:502:1ca1::30
2001:503:231d::2:30
2001:502:7094::30
2001:501:b1f9::30
2001:503:39c1::30
2001:503:d414::30

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 5/5

SUCCESS You have 13 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 7/7

SUCCESS All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers.

Nameservers on separate class C's 7/7

SUCCESS Nameservers are in a different networks.

public IPs 7/7

SUCCESS All of your NS records appear to use public IPs.

SOA

SOA record

SOA record is:
Hostmaster email
nstld.verisign-grs.com
Serial
1524189413
Refresh
1800
Retry
900
Expire
604800
TTL
900

Serial agreement 0/7

DANGER Some nameservers have a different soa serial number That can occur because of recent master update (slave have not loaded master zone yet) or the is a problem in DNS.
There is serial 1524189413 at nameserver(s) (192.5.6.30 192.54.112.30)
There is serial 1524189428 at nameserver(s) (192.42.93.30 192.41.162.30 192.52.178.30 192.26.92.30 192.31.80.30)

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: a.gtld-servers.net That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 1524189413 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 : 1800 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 : 900 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 1/1

SUCCESS SOA Expire time is : 604800 seconds. This seems OK. (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 : 900 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 com
lookup 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 com at e.gtld-servers.net(192.12.94.30) 16 ms
RECORD does not exist
Total time: 32 ms