malangkota.go.id DNS Report

Health Score: 69%

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

Checked: 1 week before

Parent

NS records at parent servers

arema.malangkota.go.id [ 222.124.213.73 ]
persema.malangkota.go.id [ 222.124.213.76 ]
satujiwa.malangkota.go.id [ 222.124.213.76 ]
aremanita.malangkota.go.id [ 222.124.213.79 ]
[These were obtained from b.dns.id.]

Glue at parent nameservers 7/7

SUCCESS Parent nameservers know A records for your domain, Very good !

NS

Mismatched glue 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(arema.malangkota.go.id.	43200	IN	A	222.124.213.73) present at Parent, missing at (222.124.213.73, 222.124.213.76)
(persema.malangkota.go.id.	43200	IN	A	222.124.213.76) present at Parent, missing at (222.124.213.73, 222.124.213.76)
(aremanita.malangkota.go.id.	43200	IN	A	222.124.213.79) present at Parent, missing at (222.124.213.73, 222.124.213.76)
(arema.malangkota.go.id.	1730	IN	A	222.124.213.76) present at (222.124.213.73, 222.124.213.73), missing at Parent
(satujiwa.malangkota.go.id.	38512	IN	A	222.124.213.76) present at (222.124.213.73), missing at Parent
(arema.malangkota.go.id.	1743	IN	A	222.124.213.76) present at (222.124.213.76), missing at Parent

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

Some nameservers does not respond:
222.124.213.79

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:
222.124.213.73

Missing (stealth) nameservers 7/7

SUCCESS All your nameservers are also listed at the parent servers.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
persema.malangkota.go.id.
aremanita.malangkota.go.id.

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
malangkota.go.id
Serial
2003021515
Refresh
1800
Retry
800
Expire
1209600
TTL
1743

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2003021515 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 : 1800 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 : 800 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 : 1743 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 malangkota.go.id
lookup malangkota.go.id at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d.dns.id(45.126.57.57)
lookup malangkota.go.id at d.dns.id(45.126.57.57) 3 ms
d.dns.id(45.126.57.57) refer to arema.malangkota.go.id(222.124.213.73)
lookup malangkota.go.id at arema.malangkota.go.id(222.124.213.73) 270 ms
got A record 'malangkota.go.id IN A 222.124.213.69' from malangkota.go.id(222.124.213.73)
Total time: 282 ms