uniregistry-dns.net DNS Report

Health Score: 70%

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

Checked: 4 years before

Parent

NS records at parent servers 

ns1.uniregistry-dns.com [ 54.205.101.85 ]
ns2.uniregistry-dns.com [ 162.242.150.89 ]
ns1.uniregistry-dns.net [ 23.253.58.227 ]
ns2.uniregistry-dns.net [ 176.34.241.253 ]
[These were obtained from e.gtld-servers.net.]

Glue at parent nameservers 7/7

SUCCESS Parent nameservers know A records for your domain, Very good !

NS

Mismatched glue 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers. 
(ns1.uniregistry-dns.com.	172800	IN	A	54.205.101.85) present at Parent, missing at (54.205.101.85, 23.253.58.227, 176.34.241.253)
(ns2.uniregistry-dns.com.	172800	IN	A	162.242.150.89) present at Parent, missing at (54.205.101.85, 23.253.58.227, 176.34.241.253)
(ns1.uniregistry-dns.net.	172800	IN	A	23.253.58.227) present at Parent, missing at (54.205.101.85, 23.253.58.227, 176.34.241.253)
(ns2.uniregistry-dns.net.	172800	IN	A	176.34.241.253) present at Parent, missing at (54.205.101.85, 23.253.58.227, 176.34.241.253)

Nameservers A records 0/7

Some servers does not provide A records for nameservers. 
missing A record(s) for (ns2.uniregistry-dns.net,ns1.uniregistry-dns.com,ns1.uniregistry-dns.net,ns2.uniregistry-dns.com) at nameserver 54.205.101.85
missing A record(s) for (ns2.uniregistry-dns.com,ns2.uniregistry-dns.net,ns1.uniregistry-dns.com,ns1.uniregistry-dns.net) at nameserver 23.253.58.227
missing A record(s) for (ns1.uniregistry-dns.net,ns2.uniregistry-dns.net,ns1.uniregistry-dns.com,ns2.uniregistry-dns.com) at nameserver 176.34.241.253

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:4800:7815:101:144f:581f:ff05:3e77

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 4 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
dns.uniregistry.net
Serial
2015012165
Refresh
300
Retry
60
Expire
604800
TTL
60

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2015012165 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: ns.uniregistry.net, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2015012165 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 0/1

WARNING SOA Retry interval is : 300 seconds. This seems too small. (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 0/1

WARNING SOA Retry interval is : 60 seconds. This seems too small. (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 0/1

WARNING SOA Expire time is : 60 seconds. This seems too small. (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 uniregistry-dns.net
lookup uniregistry-dns.net at A.ROOT-SERVERS.NET(198.41.0.4) 15 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup uniregistry-dns.net at a.gtld-servers.net(192.5.6.30) 22 ms
a.gtld-servers.net(192.5.6.30) refer to ns1.uniregistry-dns.com(54.205.101.85)
lookup uniregistry-dns.net at ns1.uniregistry-dns.com(54.205.101.85) 25 ms
RECORD does not exist
Total time: 62 ms