maiserygaard.dk DNS Report

Health Score: 76%

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

Checked: 4 months before

Parent

NS records at parent servers

ns1.gratisdns.dk [ 109.238.48.13 ]
ns2.gratisdns.dk [ 185.10.10.53 ]
ns3.gratisdns.dk [ 194.0.2.6 ]
ns4.gratisdns.dk [ 62.61.159.230 ]
ns5.gratisdns.dk [ 149.11.76.234 ]
[These were obtained from a.nic.dk.]

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.
(ns1.gratisdns.dk.	86400	IN	A	109.238.48.13) present at Parent, missing at (185.10.10.53)
(ns2.gratisdns.dk.	86400	IN	A	185.10.10.53) present at Parent, missing at (185.10.10.53)
(ns3.gratisdns.dk.	86400	IN	A	194.0.2.6) present at Parent, missing at (185.10.10.53)
(ns4.gratisdns.dk.	86400	IN	A	62.61.159.230) present at Parent, missing at (185.10.10.53)
(ns5.gratisdns.dk.	86400	IN	A	149.11.76.234) present at Parent, missing at (185.10.10.53)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns5.gratisdns.dk,ns4.gratisdns.dk,ns2.gratisdns.dk,ns1.gratisdns.dk,ns3.gratisdns.dk) at nameserver 185.10.10.53

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

Nameservers respond 0/10

Some nameservers does not respond:
2a02:9d0:3002:1::2
2001:678:5::6
2001:14d0::4
2001:978:2:6f::1f:53

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 5 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.gratisdns.dk
Serial
2017112301
Refresh
10800
Retry
3600
Expire
2419000
TTL
43200

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2017112301 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 : 10800 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 : 2419000 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.

Info

DNS trace

Trace to maiserygaard.dk
lookup maiserygaard.dk at A.ROOT-SERVERS.NET(198.41.0.4) 12 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.nic.dk(212.88.78.122)
lookup maiserygaard.dk at a.nic.dk(212.88.78.122) 117 ms
a.nic.dk(212.88.78.122) refer to ns1.gratisdns.dk(109.238.48.13)
lookup maiserygaard.dk at ns1.gratisdns.dk(109.238.48.13) 98 ms
got A record 'maiserygaard.dk IN A 81.7.160.122' from maiserygaard.dk(109.238.48.13)
Total time: 227 ms