premiertraining.com.my DNS Report

Health Score: 73%

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

Checked: 4 months before

Parent

NS records at parent servers

dns1.serverfreak.biz
dns2.serverfreak.biz
[These were obtained from ns2.cuhk.edu.hk.]

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 serverfreak.biz

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

WARNING You have 2 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:
dns2.hostingyupradin.com.
dns1.hostingyupradin.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
dns1.serverfreak.biz.
dns2.serverfreak.biz.

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
admin.hostingyupradin.com
Serial
2017101102
Refresh
3600
Retry
7200
Expire
1209600
TTL
86400

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2017101102 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: dns1.hostingyupradin.com, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2017101102 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 : 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 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 : 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 premiertraining.com.my
lookup premiertraining.com.my at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.mynic.net.my(49.236.194.202)
lookup premiertraining.com.my at a.mynic.net.my(49.236.194.202) 278 ms
a.mynic.net.my(49.236.194.202) refer to b.mynic.net.my(49.236.194.203)
lookup premiertraining.com.my at b.mynic.net.my(49.236.194.203) 280 ms
b.mynic.net.my(49.236.194.203) refer to dns2.serverfreak.biz(unknow IP)
extra IP lookup for dns2.serverfreak.biz at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns2.serverfreak.biz at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to k.gtld.biz(156.154.128.65)
lookup dns2.serverfreak.biz at k.gtld.biz(156.154.128.65) 33 ms
k.gtld.biz(156.154.128.65) refer to ns1.serverfreak.biz(72.9.157.209)
lookup dns2.serverfreak.biz at ns1.serverfreak.biz(72.9.157.209) 61 ms
got A record 'dns2.serverfreak.biz IN A 106.187.90.37' from dns2.serverfreak.biz(72.9.157.209)
lookup premiertraining.com.my at dns2.serverfreak.biz(106.187.90.37) 185 ms
got A record 'premiertraining.com.my IN A 220.158.200.102' from premiertraining.com.my(106.187.90.37)
Total time: 852 ms