`appdoni.ir` DNS Report

Health Score: 75%

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

Checked: 5 days before

Parent

NS records at parent servers

irdns.mercury.orderbox-dns.com
irdns.venus.orderbox-dns.com
irdns.earth.orderbox-dns.com
irdns.mars.orderbox-dns.com

[These were obtained from a.nic.ir.]

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 mercury.orderbox-dns.com Check venus.orderbox-dns.com Check earth.orderbox-dns.com Check mars.orderbox-dns.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 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:

irdns.mercury.orderbox-dns.com.
irdns.venus.orderbox-dns.com.
irdns.earth.orderbox-dns.com.
irdns.mars.orderbox-dns.com.

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.appdoni.ir
Serial: 1610591074
Refresh: 10800
Retry: 3600
Expire: 604800
TTL: 60

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 1610591074 at nameserver(s) (162.251.82.251 162.251.82.253)

There is serial 1610591071 at nameserver(s) (162.251.82.248)

There is serial 1610591072 at nameserver(s) (162.251.82.118)

SOA MNAME 0/3

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

Serial value 1/1

SUCCESS SOA serial number is: 1610591074 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 : 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 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 0/1

WARNING SOA Expire time is : 60 seconds. This seems too small. (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 appdoni.ir

lookup appdoni.ir at A.ROOT-SERVERS.NET(198.41.0.4) 4 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.nic.ir(193.189.123.2)
lookup appdoni.ir at a.nic.ir(193.189.123.2) 94 ms
a.nic.ir(193.189.123.2) refer to irdns.mars.orderbox-dns.com(unknow IP)
extra IP lookup for irdns.mars.orderbox-dns.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup irdns.mars.orderbox-dns.com at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup irdns.mars.orderbox-dns.com at a.gtld-servers.net(192.5.6.30) 6 ms
a.gtld-servers.net(192.5.6.30) refer to andy.ns.cloudflare.com(108.162.193.101)
lookup irdns.mars.orderbox-dns.com at andy.ns.cloudflare.com(108.162.193.101) 6 ms
got A record 'irdns.mars.orderbox-dns.com IN A 162.251.82.125' from irdns.mars.orderbox-dns.com(108.162.193.101)
lookup appdoni.ir at irdns.mars.orderbox-dns.com(162.251.82.125) 114 ms
got A record 'appdoni.ir IN A 208.91.197.91' from appdoni.ir(162.251.82.125)

Total time: 229 ms

appdoni.ir DNS Report