meta-technology.net DNS Report

Health Score: 69%

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

Checked: 1 month before

Parent

NS records at parent servers

ns1.cloudns.net [ 85.159.233.17 ]
ns2.cloudns.net [ 108.59.1.205 ]
ns3.cloudns.net [ 188.241.116.117 ]
ns4.cloudns.net [ 46.165.223.182 ]
[These were obtained from a.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.cloudns.net.		172800	IN	A	85.159.233.17) present at Parent, missing at (85.159.233.17, 188.241.116.117, 46.165.223.182)
(ns2.cloudns.net.		172800	IN	A	108.59.1.205) present at Parent, missing at (85.159.233.17, 188.241.116.117, 46.165.223.182)
(ns3.cloudns.net.		172800	IN	A	188.241.116.117) present at Parent, missing at (85.159.233.17, 188.241.116.117, 46.165.223.182)
(ns4.cloudns.net.		172800	IN	A	46.165.223.182) present at Parent, missing at (85.159.233.17, 188.241.116.117, 46.165.223.182)
(ns1.meta-technology.net.	3600	IN	A	202.78.195.206) present at (85.159.233.17, 188.241.116.117, 46.165.223.182), missing at Parent
(ns2.meta-technology.net.	3600	IN	A	202.78.195.206) present at (85.159.233.17, 188.241.116.117, 46.165.223.182), missing at Parent

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns2.cloudns.net,ns4.cloudns.net,ns1.cloudns.net,ns3.cloudns.net) at nameserver 85.159.233.17
missing A record(s) for (ns4.cloudns.net,ns3.cloudns.net,ns2.cloudns.net,ns1.cloudns.net) at nameserver 188.241.116.117
missing A record(s) for (ns3.cloudns.net,ns1.cloudns.net,ns2.cloudns.net,ns4.cloudns.net) at nameserver 46.165.223.182

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:
2604:9a00:2100:a001:2::1

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

DANGER There are nameservers not listed at the parent servers:
ns2.meta-technology.net.
ns1.meta-technology.net.

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
support.cloudns.net
Serial
2016082602
Refresh
7200
Retry
1800
Expire
1209600
TTL
3600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2016082602 That means that all your nameservers are using the same data.

SOA MNAME 3/3

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

Serial value 1/1

SUCCESS SOA serial number is: 2016082602 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 : 1800 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 : 1209600 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 : 3600 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 meta-technology.net
lookup meta-technology.net at A.ROOT-SERVERS.NET(198.41.0.4) 43 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup meta-technology.net at a.gtld-servers.net(192.5.6.30) 43 ms
a.gtld-servers.net(192.5.6.30) refer to ns1.cloudns.net(85.159.233.17)
lookup meta-technology.net at ns1.cloudns.net(85.159.233.17) 89 ms
got A record 'meta-technology.net IN A 202.78.195.206' from meta-technology.net(85.159.233.17)
Total time: 175 ms