tnyurl.co DNS Report

Health Score: 67%

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

Checked: 1 week before

Parent

NS records at parent servers

ns3.tnyurl.co [ 174.37.183.108 ]
ns2.tnyurl.co [ 50.22.35.226 ]
ns1.tnyurl.co [ 208.43.81.114 ]
[These were obtained from ns4.cctld.co.]

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.tnyurl.co.		3600	IN	A	208.43.81.114) present at Parent, missing at (174.37.183.108, 50.22.35.226, 208.43.81.114)
(ns2.tnyurl.co.		3600	IN	A	50.22.35.226) present at Parent, missing at (174.37.183.108, 50.22.35.226, 208.43.81.114)
(ns3.tnyurl.co.		3600	IN	A	174.37.183.108) present at Parent, missing at (174.37.183.108, 50.22.35.226, 208.43.81.114)
(ns1.speedydns.net.	86400	IN	A	208.43.81.114) present at (174.37.183.108, 50.22.35.226, 208.43.81.114), missing at Parent
(ns2.speedydns.net.	86400	IN	A	50.22.35.226) present at (174.37.183.108, 50.22.35.226, 208.43.81.114), missing at Parent

Nameservers A records 7/7

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

SUCCESS You have 3 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:
ns1.speedydns.net.
ns2.speedydns.net.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns3.tnyurl.co.
ns2.tnyurl.co.
ns1.tnyurl.co.

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
root.useast4.myserverhosts.com
Serial
2016042801
Refresh
86400
Retry
7200
Expire
3600000
TTL
86400

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 2016042801 at nameserver(s) (174.37.183.108)
There is serial 2016072912 at nameserver(s) (50.22.35.226)
There is serial 2017112701 at nameserver(s) (208.43.81.114)

SOA MNAME 0/3

DANGER SOA (Start of Authority) record states that your master (primary) name server is: ns1.speedydns.net, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2016042801 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 : 86400 seconds. This seems too big;. (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 : 3600000 seconds. This seems too big;. (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 : 86400 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 tnyurl.co
lookup tnyurl.co at A.ROOT-SERVERS.NET(198.41.0.4) 6 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to ns4.cctld.co(156.154.103.25)
lookup tnyurl.co at ns4.cctld.co(156.154.103.25) 18 ms
ns4.cctld.co(156.154.103.25) refer to ns3.tnyurl.co(174.37.183.108)
lookup tnyurl.co at ns3.tnyurl.co(174.37.183.108) 64 ms
got A record 'tnyurl.co IN A 65.75.149.194' from tnyurl.co(174.37.183.108)
Total time: 88 ms