remote.mhcb.co.uk DNS Report

Health Score: 70%

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

Checked: 1 month before

Parent

NS records at parent servers

ns1.mhcb.co.uk [ 62.254.3.234 ]
ns2.mhcb.co.uk [ 91.186.185.16 ]
[These were obtained from ns-151-a.gandi.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.
(ns1.mhcb.co.uk.		10800	IN	A	62.254.3.234) present at Parent, missing at (62.254.3.234, 91.186.185.16)
(ns2.mhcb.co.uk.		10800	IN	A	91.186.185.16) present at Parent, missing at (62.254.3.234, 91.186.185.16)
(ns2.remote.mhcb.co.uk.	28800	IN	A	91.186.185.16) present at (62.254.3.234, 91.186.185.16), missing at Parent
(ns1.remote.mhcb.co.uk.	28800	IN	A	62.254.3.234) present at (62.254.3.234, 91.186.185.16), missing at Parent

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

SUCCESS All the nameservers listed at the parent servers answer authoritatively for your domain.

Missing (stealth) nameservers 0/7

DANGER There are nameservers not listed at the parent servers:
ns2.remote.mhcb.co.uk.
ns1.remote.mhcb.co.uk.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns1.mhcb.co.uk.
ns2.mhcb.co.uk.

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
serversupport.mhcb.co.uk
Serial
100
Refresh
3600
Retry
3
Expire
3600
TTL
28800

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 100 That means that all your nameservers are using the same data.

SOA MNAME 0/3

DANGER SOA (Start of Authority) record states that your master (primary) name server is: ns1.remote.mhcb.co.uk, but that server is not listed at the parent servers.

Serial value 0/1

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

SUCCESS SOA Retry interval is : 3600 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 0/1

WARNING SOA Retry interval is : 3 seconds. This seems too small. (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 : 3600 seconds. This seems too small. (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 : 28800 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 remote.mhcb.co.uk
lookup remote.mhcb.co.uk at A.ROOT-SERVERS.NET(198.41.0.4) 8 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to dns1.nic.uk(213.248.216.1)
lookup remote.mhcb.co.uk at dns1.nic.uk(213.248.216.1) 8 ms
dns1.nic.uk(213.248.216.1) refer to ns-151-a.gandi.net(unknow IP)
extra IP lookup for ns-151-a.gandi.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns-151-a.gandi.net at A.ROOT-SERVERS.NET(198.41.0.4) 8 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup ns-151-a.gandi.net at a.gtld-servers.net(192.5.6.30) 40 ms
a.gtld-servers.net(192.5.6.30) refer to dns0.gandi.net(217.70.177.39)
lookup ns-151-a.gandi.net at dns0.gandi.net(217.70.177.39) 83 ms
got A record 'ns-151-a.gandi.net IN A 173.246.100.152' from ns-151-a.gandi.net(217.70.177.39)
lookup remote.mhcb.co.uk at ns-151-a.gandi.net(173.246.100.152) 67 ms
ns-151-a.gandi.net(173.246.100.152) refer to ns1.mhcb.co.uk(62.254.3.234)
lookup remote.mhcb.co.uk at ns1.mhcb.co.uk(62.254.3.234) 100 ms
got A record 'remote.mhcb.co.uk IN A 62.254.3.233' from remote.mhcb.co.uk(62.254.3.234)
Total time: 314 ms