muralinggau.ac.id DNS Report

Health Score: 83%

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

Checked: 3 weeks before

Parent

NS records at parent servers

ns01.cloudhost.id
ns02.cloudhost.id
[These were obtained from d.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 cloudhost.id

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns02.cloudhost.id) at nameserver 139.99.7.209
missing A record(s) for (ns02.cloudhost.id) at nameserver 103.15.226.15

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 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
admin.nightkidz.net
Serial
2019062500
Refresh
3600
Retry
1800
Expire
1209600
TTL
86400

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2019062500 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 : 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 muralinggau.ac.id
lookup muralinggau.ac.id at A.ROOT-SERVERS.NET(198.41.0.4) 41 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d.dns.id(45.126.57.57)
lookup muralinggau.ac.id at d.dns.id(45.126.57.57) 83 ms
d.dns.id(45.126.57.57) refer to ns02.cloudhost.id(unknow IP)
extra IP lookup for ns02.cloudhost.id at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns02.cloudhost.id at A.ROOT-SERVERS.NET(198.41.0.4) 36 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d.dns.id(45.126.57.57)
lookup ns02.cloudhost.id at d.dns.id(45.126.57.57) 75 ms
d.dns.id(45.126.57.57) refer to sara.ns.cloudflare.com(unknow IP)
extra IP lookup for sara.ns.cloudflare.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup sara.ns.cloudflare.com at A.ROOT-SERVERS.NET(198.41.0.4) 37 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup sara.ns.cloudflare.com at a.gtld-servers.net(192.5.6.30) 38 ms
a.gtld-servers.net(192.5.6.30) refer to ns3.cloudflare.com(162.159.0.33)
lookup sara.ns.cloudflare.com at ns3.cloudflare.com(162.159.0.33) 3 ms
got A record 'sara.ns.cloudflare.com IN A 173.245.58.144' from sara.ns.cloudflare.com(162.159.0.33)
lookup ns02.cloudhost.id at sara.ns.cloudflare.com(173.245.58.144) 3 ms
got A record 'ns02.cloudhost.id IN A 103.15.226.15' from ns02.cloudhost.id(173.245.58.144)
lookup muralinggau.ac.id at ns02.cloudhost.id(103.15.226.15) 247 ms
got A record 'muralinggau.ac.id IN A 139.99.21.240' from muralinggau.ac.id(103.15.226.15)
Total time: 563 ms