bmdns.net DNS Report

Health Score: 86%

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

Checked: 1 month before

Parent

NS records at parent servers

ns1.bangmod.cloud
ns2.bangmod.cloud
ns3.bangmod.cloud
ns4.bangmod.cloud
[These were obtained from a.gtld-servers.net.]

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

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
chakree.bangmod.co.th
Serial
2019101501
Refresh
1200
Retry
120
Expire
604800
TTL
300

Serial agreement 0/7

DANGER Some nameservers have a different soa serial number That can occur because of recent master update (slave have not loaded master zone yet) or the is a problem in DNS.
There is serial 2019101501 at nameserver(s) (103.27.200.3)
There is serial 2019101502 at nameserver(s) (139.99.105.43)
There is serial 2019101503 at nameserver(s) (66.70.188.206)
There is serial 2019101504 at nameserver(s) (51.77.245.238)

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: ns1.bangmod.cloud That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2019101501 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 : 1200 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 : 120 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 : 604800 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 : 300 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 bmdns.net
lookup bmdns.net at A.ROOT-SERVERS.NET(198.41.0.4) 72 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup bmdns.net at a.gtld-servers.net(192.5.6.30) 88 ms
a.gtld-servers.net(192.5.6.30) refer to ns4.bangmod.cloud(unknow IP)
extra IP lookup for ns4.bangmod.cloud at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns4.bangmod.cloud at A.ROOT-SERVERS.NET(198.41.0.4) 71 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d.nic.cloud(37.209.198.10)
lookup ns4.bangmod.cloud at d.nic.cloud(37.209.198.10) 42 ms
d.nic.cloud(37.209.198.10) refer to ns4.bangmod.cloud(51.77.245.238)
lookup ns4.bangmod.cloud at ns4.bangmod.cloud(51.77.245.238) 88 ms
got A record 'ns4.bangmod.cloud IN A 51.77.245.238' from ns4.bangmod.cloud(51.77.245.238)
lookup bmdns.net at ns4.bangmod.cloud(51.77.245.238) 88 ms
got A record 'bmdns.net IN A 103.27.203.10' from bmdns.net(51.77.245.238)
Total time: 449 ms