up.ac.mz DNS Report

Health Score: 75%

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

Checked: 4 months before

Parent

NS records at parent servers

dns2.up.ac.mz [ 196.3.99.109 ]
ns.up.ac.mz [ 196.3.99.97 ]
[These were obtained from oceano.uem.mz.]

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.
(cead.up.ac.mz.		43200	IN	A	196.3.99.102) present at (196.3.99.109, 196.3.99.97), missing at Parent
(ciup.up.ac.mz.		43200	IN	A	196.3.99.101) present at (196.3.99.109, 196.3.99.97), missing at Parent
(estec.up.ac.mz.		43200	IN	A	196.3.99.98) present at (196.3.99.109, 196.3.99.97), missing at Parent
(edondzo.up.ac.mz.	43200	IN	A	196.3.99.100) present at (196.3.99.109, 196.3.99.97), missing at Parent
(kukhomo.up.ac.mz.	43200	IN	A	196.3.99.108) present at (196.3.99.109, 196.3.99.97), missing at Parent
(kayakweru.up.ac.mz.	43200	IN	A	196.3.99.101) present at (196.3.99.109, 196.3.99.97), missing at Parent
(ulimwengo.up.ac.mz.	43200	IN	A	196.3.99.98) present at (196.3.99.109, 196.3.99.97), missing at Parent
(dzivangutu.up.ac.mz.	43200	IN	A	196.3.99.101) present at (196.3.99.109, 196.3.99.97), missing at Parent
(dzowo.uem.mz.		13225	IN	A	196.3.96.66) present at (196.3.99.97), missing at Parent
(oceano.uem.mz.		5003	IN	A	196.3.96.69) present at (196.3.99.97), missing at Parent

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (dzowo.uem.mz,oceano.uem.mz,dsdi-pc.up.ac.mz) at nameserver 196.3.99.109
missing A record(s) for (dsdi-pc.up.ac.mz) at nameserver 196.3.99.97

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 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 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:
edondzo.up.ac.mz.
estec.up.ac.mz.
dzowo.uem.mz.
ciup.up.ac.mz.
kukhomo.up.ac.mz.
oceano.uem.mz.
dsdi-pc.up.ac.mz.
ulimwengo.up.ac.mz.
kayakweru.up.ac.mz.
dzivangutu.up.ac.mz.
cead.up.ac.mz.

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
ciup.up.ac.mz
Serial
2013102412
Refresh
43200
Retry
86400
Expire
2419200
TTL
43200

Serial agreement 7/7

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

SOA MNAME 3/3

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

Serial value 1/1

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

WARNING SOA Retry interval is : 86400 seconds. This seems too big;. (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 : 43200 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.