theturkhost.net DNS Report

Health Score: 69%

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

Checked: 2 months before

Parent

NS records at parent servers

ns1.cpanellinux.com
ns2.cpanellinux.com
ns3.cpanellinux.com
[These were obtained from e.gtld-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 7/7

Skip glue checking. Make sure the nameservers domain is good standing Check cpanellinux.com

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

The NS records at your nameservers are different
At (208.91.197.91) there are nameservers: ns1391.ztomy.com. ns2391.ztomy.com.
At (46.45.162.113) there are nameservers: ns1.cpanellinux.com. ns3.cpanellinux.com. ns2.cpanellinux.com.

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:
ns1391.ztomy.com.
ns2391.ztomy.com.

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
abuse.opticaljungle.com
Serial
2011062801
Refresh
3600
Retry
900
Expire
604800
TTL
300

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 2011062801 at nameserver(s) (208.91.197.91)
There is serial 2017020201 at nameserver(s) (46.45.162.113)

SOA MNAME 0/3

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

Serial value 1/1

SUCCESS SOA serial number is: 2011062801 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 : 3600 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 : 300 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 theturkhost.net
lookup theturkhost.net at A.ROOT-SERVERS.NET(198.41.0.4) 75 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup theturkhost.net at a.gtld-servers.net(192.5.6.30) 79 ms
a.gtld-servers.net(192.5.6.30) refer to ns3.cpanellinux.com(unknow IP)
extra IP lookup for ns3.cpanellinux.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns3.cpanellinux.com at A.ROOT-SERVERS.NET(198.41.0.4) 79 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup ns3.cpanellinux.com at e.gtld-servers.net(192.12.94.30) 23 ms
e.gtld-servers.net(192.12.94.30) refer to ns1.cpanellinux.com(46.45.162.112)
lookup ns3.cpanellinux.com at ns1.cpanellinux.com(46.45.162.112) 128 ms
got A record 'ns3.cpanellinux.com IN A 46.45.162.114' from ns3.cpanellinux.com(46.45.162.112)
lookup theturkhost.net at ns3.cpanellinux.com(46.45.162.114) 129 ms
got A record 'theturkhost.net IN A 46.45.162.112' from theturkhost.net(46.45.162.114)
Total time: 513 ms