bangtot.vn DNS Report

Health Score: 86%

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

Checked: 9 months before

Parent

NS records at parent servers

ns3.seolover.cloud
ns2.seolover.cloud
ns1.seolover.cloud
[These were obtained from d.dns-servers.vn.]

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 seolover.cloud

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.seolover.cloud,ns2.seolover.cloud,ns3.seolover.cloud) at nameserver 163.44.154.27
missing A record(s) for (ns3.seolover.cloud,ns1.seolover.cloud,ns2.seolover.cloud) at nameserver 118.27.22.108
missing A record(s) for (ns1.seolover.cloud,ns2.seolover.cloud,ns3.seolover.cloud) at nameserver 163.44.193.123

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 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
hostmaster.bangtot.vn
Serial
2019072601
Refresh
7200
Retry
1800
Expire
1209600
TTL
86400

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2019072601 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.seolover.cloud That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2019072601 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 : 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 bangtot.vn
lookup bangtot.vn at A.ROOT-SERVERS.NET(198.41.0.4) 44 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns-servers.vn(194.0.1.18)
lookup bangtot.vn at a.dns-servers.vn(194.0.1.18) 3 ms
a.dns-servers.vn(194.0.1.18) refer to ns3.seolover.cloud(unknow IP)
extra IP lookup for ns3.seolover.cloud at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns3.seolover.cloud at A.ROOT-SERVERS.NET(198.41.0.4) 43 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.nic.cloud(37.209.192.10)
lookup ns3.seolover.cloud at a.nic.cloud(37.209.192.10) 10 ms
a.nic.cloud(37.209.192.10) refer to ns3.tenten.vn(unknow IP)
extra IP lookup for ns3.tenten.vn at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns3.tenten.vn at A.ROOT-SERVERS.NET(198.41.0.4) 48 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns-servers.vn(194.0.1.18)
lookup ns3.tenten.vn at a.dns-servers.vn(194.0.1.18) 3 ms
a.dns-servers.vn(194.0.1.18) refer to ns1.tenten.vn(103.18.7.201)
lookup ns3.tenten.vn at ns1.tenten.vn(103.18.7.201) 301 ms
got A record 'ns3.tenten.vn IN A 133.130.107.205' from ns3.tenten.vn(103.18.7.201)
lookup ns3.seolover.cloud at ns3.tenten.vn(133.130.107.205) 158 ms
got A record 'ns3.seolover.cloud IN A 163.44.154.27' from ns3.seolover.cloud(133.130.107.205)
lookup bangtot.vn at ns3.seolover.cloud(163.44.154.27) 270 ms
got A record 'bangtot.vn IN A 163.44.192.154' from bangtot.vn(163.44.154.27)
Total time: 880 ms