ristoranti.guide DNS Report

Health Score: 60%

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

Checked: 2 months before

Parent

NS records at parent servers

parking1.mdnsservice.com
parking2.mdnsservice.com
[These were obtained from demand.beta.aridns.net.au.]

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

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (parking2.mdnsservice.com,parking1.mdnsservice.com) at nameserver 64.99.97.39

Nameservers report identical NS records 0/7

The NS records at your nameservers are different
At (64.99.97.39) there are nameservers: parking2.mdnsservice.com. parking1.mdnsservice.com.
At (64.98.148.19) there are nameservers:

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 2/5

WARNING You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.

Lame nameservers 0/7

Lame nameservers:
64.98.148.19

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.mdnsservice.com
Serial
2014091800
Refresh
86400
Retry
7200
Expire
2592000
TTL
86400

Serial agreement 0/7

DANGER Some nameservers have a different soa serial number That can occur because of recent master update (slave have not loaded master zone yet) or the is a problem in DNS.
There is serial 2014091800 at nameserver(s) (64.99.97.39)
There is serial at nameserver(s) (64.98.148.19)

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: parking1.mdnsservice.com That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2014091800 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 : 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 : 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 ristoranti.guide
lookup ristoranti.guide at A.ROOT-SERVERS.NET(198.41.0.4) 8 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to demand.alpha.aridns.net.au(37.209.192.7)
lookup ristoranti.guide at demand.alpha.aridns.net.au(37.209.192.7) 82 ms
demand.alpha.aridns.net.au(37.209.192.7) refer to parking2.mdnsservice.com(unknow IP)
extra IP lookup for parking2.mdnsservice.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup parking2.mdnsservice.com at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup parking2.mdnsservice.com at e.gtld-servers.net(192.12.94.30) 9 ms
e.gtld-servers.net(192.12.94.30) refer to dns1.tucows.com(216.40.47.20)
lookup parking2.mdnsservice.com at dns1.tucows.com(216.40.47.20) 30 ms
got A record 'parking2.mdnsservice.com IN A 64.98.148.19' from parking2.mdnsservice.com(216.40.47.20)
lookup ristoranti.guide at parking2.mdnsservice.com(64.98.148.19) 8 ms
parking2.mdnsservice.com(64.98.148.19) refer to m.root-servers.net(unknow IP)
extra IP lookup for m.root-servers.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup m.root-servers.net at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
got A record 'm.root-servers.net IN A 202.12.27.33' from m.root-servers.net(198.41.0.4)
lookup ristoranti.guide at m.root-servers.net(202.12.27.33) 83 ms
m.root-servers.net(202.12.27.33) refer to demand.alpha.aridns.net.au(37.209.192.7)
lookup ristoranti.guide at demand.alpha.aridns.net.au(37.209.192.7) 79 ms
demand.alpha.aridns.net.au(37.209.192.7) refer to parking1.mdnsservice.com(unknow IP)
extra IP lookup for parking1.mdnsservice.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup parking1.mdnsservice.com at A.ROOT-SERVERS.NET(198.41.0.4) 9 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup parking1.mdnsservice.com at e.gtld-servers.net(192.12.94.30) 8 ms
e.gtld-servers.net(192.12.94.30) refer to dns1.tucows.com(216.40.47.20)
lookup parking1.mdnsservice.com at dns1.tucows.com(216.40.47.20) 29 ms
got A record 'parking1.mdnsservice.com IN A 64.99.97.39' from parking1.mdnsservice.com(216.40.47.20)
lookup ristoranti.guide at parking1.mdnsservice.com(64.99.97.39) 29 ms
got A record 'ristoranti.guide IN A 208.91.197.160' from ristoranti.guide(64.99.97.39)
Total time: 392 ms