servage.net DNS Report

Health Score: 86%

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

Checked: 2 years before

Parent

NS records at parent servers 

ns1.servage.net [ 77.232.76.16 ]
ns2.servage.net [ 83.168.192.66 ]
ns3.servage.net [ 77.232.66.6 ]
ns4.servage.net [ 77.232.81.1 ]
ns5.servage.net [ 77.232.76.13 ]
ns6.servage.net [ 83.168.192.66 ]
[These were obtained from a.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. 
(ns5.servage.net.		172800	IN	A	77.232.76.13) present at Parent, missing at (77.232.76.16, 83.168.192.66, 77.232.66.6, 77.232.81.1, 77.232.76.13)
(ns6.servage.net.		172800	IN	A	83.168.192.66) present at Parent, missing at (77.232.76.16, 83.168.192.66, 77.232.66.6, 77.232.81.1, 77.232.76.13)

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 6 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: 
ns5.servage.net.
ns6.servage.net.

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.servage.net
Serial
2018102400
Refresh
21600
Retry
3600
Expire
1209600
TTL
300

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2018102400 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.servage.net That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2018102400 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 : 21600 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 : 300 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 servage.net
lookup servage.net at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup servage.net at e.gtld-servers.net(192.12.94.30) 9 ms
e.gtld-servers.net(192.12.94.30) refer to ns1.servage.net(77.232.76.16)
lookup servage.net at ns1.servage.net(77.232.76.16) 87 ms
got A record 'servage.net IN A 77.232.66.2' from servage.net(77.232.76.16)
Total time: 107 ms