studiomdm.eu DNS Report

Health Score: 83%

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

Checked: 3 months before

Parent

NS records at parent servers 

dns.technorail.com
dns2.technorail.com
dns4.arubadns.cz
dns3.arubadns.net
[These were obtained from x.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 technorail.com Check arubadns.cz Check arubadns.net

Nameservers A records 0/7

Some servers does not provide A records for nameservers. 
missing A record(s) for (dns.technorail.com,dns2.technorail.com,dns4.arubadns.cz) at nameserver 62.149.128.2
missing A record(s) for (dns4.arubadns.cz,dns.technorail.com,dns2.technorail.com) at nameserver 62.149.132.2
missing A record(s) for (dns4.arubadns.cz,dns.technorail.com,dns2.technorail.com) at nameserver 81.2.199.73
missing A record(s) for (dns2.technorail.com,dns.technorail.com,dns4.arubadns.cz) at nameserver 95.110.220.5

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 4 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
hostmaster.technorail.com
Serial
1
Refresh
86400
Retry
7200
Expire
2592000
TTL
21600

Serial agreement 7/7

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

Serial value 0/1

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

WARNING SOA Expire time is : 2592000 seconds. This seems too big;. (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 : 21600 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 studiomdm.eu
lookup studiomdm.eu at A.ROOT-SERVERS.NET(198.41.0.4) 76 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to cz.dns.eu(93.190.128.138)
lookup studiomdm.eu at cz.dns.eu(93.190.128.138) 107 ms
cz.dns.eu(93.190.128.138) refer to dns4.arubadns.cz(unknow IP)
extra IP lookup for dns4.arubadns.cz at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns4.arubadns.cz at A.ROOT-SERVERS.NET(198.41.0.4) 77 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to b.ns.nic.cz(194.0.13.1)
lookup dns4.arubadns.cz at b.ns.nic.cz(194.0.13.1) 105 ms
b.ns.nic.cz(194.0.13.1) refer to arudns2.aruba.it(unknow IP)
extra IP lookup for arudns2.aruba.it at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup arudns2.aruba.it at A.ROOT-SERVERS.NET(198.41.0.4) 78 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.it(194.0.16.215)
lookup arudns2.aruba.it at a.dns.it(194.0.16.215) 3 ms
a.dns.it(194.0.16.215) refer to arudns1.aruba.it(62.149.128.7)
lookup arudns2.aruba.it at arudns1.aruba.it(62.149.128.7) 105 ms
got A record 'arudns2.aruba.it IN A 62.149.132.7' from arudns2.aruba.it(62.149.128.7)
lookup dns4.arubadns.cz at arudns2.aruba.it(62.149.132.7) 110 ms
got A record 'dns4.arubadns.cz IN A 81.2.199.73' from dns4.arubadns.cz(62.149.132.7)
lookup studiomdm.eu at dns4.arubadns.cz(81.2.199.73) 106 ms
got A record 'studiomdm.eu IN A 62.149.142.206' from studiomdm.eu(81.2.199.73)
Total time: 767 ms