iiserb.ac.in DNS Report

Health Score: 61%

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

Checked: 10 months before

Parent

NS records at parent servers

ns1.iiserb.ac.in [ 203.18.51.11 ]
ns3.iiserb.ac.in [ 203.18.51.12 ]
ns2.iiserb.ac.in [ 122.252.238.54 ]
[These were obtained from a0.in.afilias-nst.info.]

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.iiserb.ac.in.	86400	IN	A	203.18.51.11) present at Parent, missing at (203.18.51.12)
(ns2.iiserb.ac.in.	86400	IN	A	122.252.238.54) present at Parent, missing at (203.18.51.12)
(ns3.iiserb.ac.in.	86400	IN	A	203.18.51.12) present at Parent, missing at (203.18.51.12)

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 (203.18.51.11) there are nameservers: ns3.iiserb.ac.in. ns1.iiserb.ac.in. ns2.iiserb.ac.in.
At (203.18.51.12) there are nameservers:

Nameservers respond 0/10

Some nameservers does not respond:
122.252.238.54

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 3 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:
203.18.51.12

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
root.ns1.iiserb.ac.in
Serial
201708071
Refresh
10800
Retry
3600
Expire
1209600
TTL
86400

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 201708071 at nameserver(s) (203.18.51.11)
There is serial at nameserver(s) (203.18.51.12)

SOA MNAME 3/3

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

Serial value 0/1

WARNING SOA serial number is: 201708071 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 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 : 86400 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 iiserb.ac.in
lookup iiserb.ac.in at A.ROOT-SERVERS.NET(198.41.0.4) 6 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.in.afilias-nst.info(199.7.87.1)
lookup iiserb.ac.in at a0.in.afilias-nst.info(199.7.87.1) 169 ms
a0.in.afilias-nst.info(199.7.87.1) refer to ns1.iiserb.ac.in(203.18.51.11)
lookup iiserb.ac.in at ns1.iiserb.ac.in(203.18.51.11) 211 ms
got A record 'iiserb.ac.in IN A 203.18.51.16' from iiserb.ac.in(203.18.51.11)
Total time: 386 ms