viva.co.id DNS Report

Health Score: 91%

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

Checked: 2 months before

Parent

NS records at parent servers

dns1.vivagroup.co.id
dns2.vivagroup.co.id
dns3.vivagroup.co.id
dns4.vivagroup.co.id
[These were obtained from b.dns.id.]

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 vivagroup.co.id

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 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 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.vivagroup.co.id
Serial
2017042103
Refresh
86400
Retry
7200
Expire
3600000
TTL
86400

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2017042103 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: dns1.vivagroup.co.id That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2017042103 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 viva.co.id
lookup viva.co.id at A.ROOT-SERVERS.NET(198.41.0.4) 3 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to b.dns.id(103.19.179.179)
lookup viva.co.id at b.dns.id(103.19.179.179) 253 ms
b.dns.id(103.19.179.179) refer to dns4.vivagroup.co.id(unknow IP)
extra IP lookup for dns4.vivagroup.co.id at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns4.vivagroup.co.id at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.id(202.155.30.227)
lookup dns4.vivagroup.co.id at a.dns.id(202.155.30.227) 259 ms
a.dns.id(202.155.30.227) refer to b.dns.id(103.19.179.179)
lookup dns4.vivagroup.co.id at b.dns.id(103.19.179.179) 251 ms
b.dns.id(103.19.179.179) refer to grace.ns.cloudflare.com(unknow IP)
extra IP lookup for grace.ns.cloudflare.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup grace.ns.cloudflare.com at A.ROOT-SERVERS.NET(198.41.0.4) 7 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup grace.ns.cloudflare.com at e.gtld-servers.net(192.12.94.30) 39 ms
e.gtld-servers.net(192.12.94.30) refer to ns3.cloudflare.com(162.159.0.33)
lookup grace.ns.cloudflare.com at ns3.cloudflare.com(162.159.0.33) 4 ms
got A record 'grace.ns.cloudflare.com IN A 173.245.58.159' from grace.ns.cloudflare.com(162.159.0.33)
lookup dns4.vivagroup.co.id at grace.ns.cloudflare.com(173.245.58.159) 4 ms
got A record 'dns4.vivagroup.co.id IN A 203.130.242.174' from dns4.vivagroup.co.id(173.245.58.159)
lookup viva.co.id at dns4.vivagroup.co.id(203.130.242.174) 262 ms
got A record 'viva.co.id IN A 202.129.216.26' from viva.co.id(203.130.242.174)
Total time: 1086 ms