mokposarang.org DNS Report

Health Score: 74%

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

Checked: 2 months before

Parent

NS records at parent servers

ns2.cafe24.co.kr
ns1.cafe24.co.kr
ns1.cafe24.com
ns2.cafe24.com
[These were obtained from a0.org.afilias-nst.info.]

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 cafe24.co.kr Check cafe24.com

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

DANGER There are nameservers not listed at the parent servers:
ns.cafe24.com.
ns0.cafe24.com.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns2.cafe24.co.kr.
ns1.cafe24.co.kr.

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
postmaster.mokposarang.org
Serial
20110614
Refresh
10800
Retry
3600
Expire
3600000
TTL
1800

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 20110614 That means that all your nameservers are using the same data.

SOA MNAME 0/3

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

Serial value 0/1

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

SUCCESS SOA Retry interval is : 10800 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 : 3600 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 : 1800 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 mokposarang.org
lookup mokposarang.org at A.ROOT-SERVERS.NET(198.41.0.4) 13 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.org.afilias-nst.info(199.19.56.1)
lookup mokposarang.org at a0.org.afilias-nst.info(199.19.56.1) 160 ms
a0.org.afilias-nst.info(199.19.56.1) refer to ns2.cafe24.co.kr(unknow IP)
extra IP lookup for ns2.cafe24.co.kr at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.cafe24.co.kr at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to b.dns.kr(61.74.75.1)
lookup ns2.cafe24.co.kr at b.dns.kr(61.74.75.1) 214 ms
b.dns.kr(61.74.75.1) refer to ns1.cafe24.com(unknow IP)
extra IP lookup for ns1.cafe24.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.cafe24.com at A.ROOT-SERVERS.NET(198.41.0.4) 13 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup ns1.cafe24.com at e.gtld-servers.net(192.12.94.30) 14 ms
e.gtld-servers.net(192.12.94.30) refer to ns3.cafe24.com(112.175.11.2)
lookup ns1.cafe24.com at ns3.cafe24.com(112.175.11.2) 214 ms
got A record 'ns1.cafe24.com IN A 175.125.93.134' from ns1.cafe24.com(112.175.11.2)
lookup ns2.cafe24.co.kr at ns1.cafe24.com(175.125.93.134) 216 ms
got A record 'ns2.cafe24.co.kr IN A 112.175.247.233' from ns2.cafe24.co.kr(175.125.93.134)
lookup mokposarang.org at ns2.cafe24.co.kr(112.175.247.233) 213 ms
got A record 'mokposarang.org IN A 118.218.219.63' from mokposarang.org(112.175.247.233)
Total time: 1068 ms