phapthihoi.org DNS Report

Health Score: 57%

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

Checked: 3 months before

Parent

NS records at parent servers

nsbak.pavietnam.net
ns1.crazydomains.com
ns2.pavietnam.vn
ns1.pavietnam.vn
[These were obtained from d0.org.afilias-nst.org.]

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 pavietnam.net Check crazydomains.com Check pavietnam.vn

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.crazydomains.com) at nameserver 112.213.89.22
missing A record(s) for (ns1.crazydomains.com) at nameserver 222.255.121.247
missing A record(s) for (ns1.crazydomains.com) at nameserver 112.213.89.3

Nameservers report identical NS records 0/7

The NS records at your nameservers are different
At (112.213.89.22 222.255.121.247 112.213.89.3) there are nameservers: nsbak.pavietnam.net. ns1.crazydomains.com. ns1.pavietnam.vn. ns2.pavietnam.vn.
At (27.124.125.7) there are nameservers:

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

Lame nameservers:
27.124.125.7

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
Serial
Refresh
Retry
Expire
TTL

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 at nameserver(s) (27.124.125.7)
There is serial 2017111114 at nameserver(s) (222.255.121.247)
There is serial 2017112114 at nameserver(s) (112.213.89.3)

SOA MNAME 0/3

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

Serial value 0/1

WARNING SOA serial number is: This not 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 : 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 : 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 0/1

WARNING SOA Expire time is : seconds. This seems too small. (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 : 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 phapthihoi.org
lookup phapthihoi.org at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.org.afilias-nst.info(199.19.56.1)
lookup phapthihoi.org at a0.org.afilias-nst.info(199.19.56.1) 160 ms
a0.org.afilias-nst.info(199.19.56.1) refer to ns1.pavietnam.vn(unknow IP)
extra IP lookup for ns1.pavietnam.vn at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.pavietnam.vn at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d.dns-servers.vn(203.119.44.105)
lookup ns1.pavietnam.vn at d.dns-servers.vn(203.119.44.105) 268 ms
d.dns-servers.vn(203.119.44.105) refer to ns2.pavietnam.vn(222.255.121.247)
lookup ns1.pavietnam.vn at ns2.pavietnam.vn(222.255.121.247) 301 ms
got A record 'ns1.pavietnam.vn IN A 112.213.89.3' from ns1.pavietnam.vn(222.255.121.247)
lookup phapthihoi.org at ns1.pavietnam.vn(112.213.89.3) 234 ms
got A record 'phapthihoi.org IN A 199.189.86.37' from phapthihoi.org(112.213.89.3)
Total time: 982 ms