mdevice.eu DNS Report

Health Score: 85%

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

Checked: 1 month before

Parent

NS records at parent servers

ns1.vpsserver.com
ns3.vpsserver.com
ns2.vpsserver.com
[These were obtained from y.dns.eu.]

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 vpsserver.com

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns2.vpsserver.com,ns1.vpsserver.com,ns3.vpsserver.com) at nameserver 185.144.156.7
missing A record(s) for (ns2.vpsserver.com,ns1.vpsserver.com,ns3.vpsserver.com) at nameserver 185.144.157.253
missing A record(s) for (ns3.vpsserver.com,ns2.vpsserver.com,ns1.vpsserver.com) at nameserver 212.114.111.197

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
admin.vpsserver.com
Serial
2019121200
Refresh
86400
Retry
3600
Expire
604800
TTL
300

Serial agreement 7/7

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

Serial value 1/1

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

WARNING SOA Retry interval is : 86400 seconds. This seems too big;. (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 : 604800 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 mdevice.eu
lookup mdevice.eu at A.ROOT-SERVERS.NET(198.41.0.4) 42 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to w.dns.eu(194.0.25.28)
lookup mdevice.eu at w.dns.eu(194.0.25.28) 2 ms
w.dns.eu(194.0.25.28) refer to ns3.vpsserver.com(unknow IP)
extra IP lookup for ns3.vpsserver.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns3.vpsserver.com at A.ROOT-SERVERS.NET(198.41.0.4) 44 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup ns3.vpsserver.com at e.gtld-servers.net(192.12.94.30) 24 ms
e.gtld-servers.net(192.12.94.30) refer to tara.ns.cloudflare.com(173.245.58.225)
lookup ns3.vpsserver.com at tara.ns.cloudflare.com(173.245.58.225) 4 ms
got A record 'ns3.vpsserver.com IN A 185.144.157.253' from ns3.vpsserver.com(173.245.58.225)
lookup mdevice.eu at ns3.vpsserver.com(185.144.157.253) 53 ms
RECORD does not exist
Total time: 169 ms