cvcitc.edu.ph 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.zoom.ph
ns3.zoom.ph
ns2.zoom.ph
[These were obtained from evans.gov.ph.]

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 zoom.ph

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns3.zoom.ph) at nameserver 162.254.149.80
missing A record(s) for (ns3.zoom.ph) at nameserver 23.111.170.34
missing A record(s) for (ns3.zoom.ph) at nameserver 216.12.221.36

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 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 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
localhost-notifs.localhost-notifs-genes.com
Serial
2020021106
Refresh
3600
Retry
1800
Expire
1209600
TTL
86400

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2020021106 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: ns1.zoom.ph That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2020021106 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 : 1800 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 cvcitc.edu.ph
lookup cvcitc.edu.ph at A.ROOT-SERVERS.NET(198.41.0.4) 43 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to 1.ns.ph(206.51.255.1)
lookup cvcitc.edu.ph at 1.ns.ph(206.51.255.1) 4 ms
1.ns.ph(206.51.255.1) refer to gomez.ph.net(unknow IP)
extra IP lookup for gomez.ph.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup gomez.ph.net at A.ROOT-SERVERS.NET(198.41.0.4) 51 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup gomez.ph.net at a.gtld-servers.net(192.5.6.30) 43 ms
a.gtld-servers.net(192.5.6.30) refer to gabriela.ph.net(165.220.3.7)
lookup gomez.ph.net at gabriela.ph.net(165.220.3.7) 209 ms
got A record 'gomez.ph.net IN A 165.220.1.1' from gomez.ph.net(165.220.3.7)
lookup cvcitc.edu.ph at gomez.ph.net(165.220.1.1) 213 ms
gomez.ph.net(165.220.1.1) refer to ns1.zoom.ph(unknow IP)
extra IP lookup for ns1.zoom.ph at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.zoom.ph at A.ROOT-SERVERS.NET(198.41.0.4) 43 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to ns4.apnic.net(202.12.31.53)
lookup ns1.zoom.ph at ns4.apnic.net(202.12.31.53) 80 ms
ns4.apnic.net(202.12.31.53) refer to ns6.domains.ph(76.74.154.236)
lookup ns1.zoom.ph at ns6.domains.ph(76.74.154.236) 84 ms
got A record 'ns1.zoom.ph IN A 162.254.149.80' from ns1.zoom.ph(76.74.154.236)
lookup cvcitc.edu.ph at ns1.zoom.ph(162.254.149.80) 39 ms
got A record 'cvcitc.edu.ph IN A 23.92.68.146' from cvcitc.edu.ph(162.254.149.80)
Total time: 809 ms