domainesia.net DNS Report

Health Score: 69%

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

Checked: 1 month before

Parent

NS records at parent servers

ns1.domainesia.net [ 203.114.74.128 213.52.129.108 96.126.118.18 ]
ns2.domainesia.net [ 139.162.112.224 172.104.180.98 213.52.129.108 ]
[These were obtained from e.gtld-servers.net.]

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.
(ns1.domainesia.net.	172800	IN	A	213.52.129.108) present at Parent, missing at (96.126.118.18, 213.52.129.108)
(ns2.domainesia.net.	172800	IN	A	213.52.129.108) present at Parent, missing at (96.126.118.18, 213.52.129.108)
(ns1.domainesia.net.	172800	IN	A	203.114.74.128) present at Parent, missing at (213.52.129.108)
(ns1.domainesia.net.	172800	IN	A	96.126.118.18) present at Parent, missing at (213.52.129.108)
(ns2.domainesia.net.	172800	IN	A	139.162.112.224) present at Parent, missing at (213.52.129.108)
(ns2.domainesia.net.	172800	IN	A	172.104.180.98) present at Parent, missing at (213.52.129.108)

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

The NS records at your nameservers are different
At (96.126.118.18) there are nameservers: ns2.domainesia.net. ns1.domainesia.net.
At (213.52.129.108) there are nameservers:

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

Lame nameservers:
213.52.129.108

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
fuad.simszone.org
Serial
2019041705
Refresh
3600
Retry
300
Expire
2419200
TTL
1800

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 2019041705 at nameserver(s) (96.126.118.18)
There is serial at nameserver(s) (213.52.129.108)

SOA MNAME 3/3

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

Serial value 1/1

SUCCESS SOA serial number is: 2019041705 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 : 300 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 : 2419200 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 : 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 domainesia.net
lookup domainesia.net at A.ROOT-SERVERS.NET(198.41.0.4) 38 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup domainesia.net at a.gtld-servers.net(192.5.6.30) 36 ms
a.gtld-servers.net(192.5.6.30) refer to ns1.domainesia.net(203.114.74.128)
lookup domainesia.net at ns1.domainesia.net(203.114.74.128) 259 ms
got A record 'domainesia.net IN A 139.162.55.180' from domainesia.net(203.114.74.128)
Total time: 333 ms