Work in progress!

Follow IntoDNS on Twitter


Category Status Test name Information
Parent Info Domain NS records Nameserver records returned by the parent servers are:

ns1.blogdir.co.uk.   ['51.89.145.77']   [TTL=172800]
ns.blogdir.co.uk.   ['51.89.145.76']   [TTL=172800]

nsb.nic.uk was kind enough to give us that information.

Warn TLD Parent Check WARNING: Looks like the parent servers do not have information for your TLD when asked. This is ok but can be confusing.
Pass Your nameservers are listed Good. The parent server nsb.nic.uk has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
Pass DNS Parent sent Glue Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3)
Pass Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.
NS Info NS records from your nameserversNS records got from your nameservers listed at the parent NS are:

ns.blogdir.co.uk  ['51.89.145.76']   [TTL=300]
ns1.blogdir.co.uk  ['51.89.145.76']   [TTL=300]

Pass Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Warn Same Glue Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.I detected some problems as follows:
For ns1.blogdir.co.uk the parent reported: ['51.89.145.76'] and your nameservers reported: ['51.89.145.76']
Pass Glue for NS records OK. When I asked your nameservers for your NS records they also returned the A records for the NS records. This is a good thing as it will spare an extra A lookup needed to find those A records.
Pass Mismatched NS records OK. The NS records at all your nameservers are identical.
Error DNS servers responded ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
51.89.145.77
Pass Name of nameservers are valid OK. All of the NS records that your nameservers report seem valid.
Pass Multiple Nameservers Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
Pass Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
Pass Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers.
Pass Missing nameservers reported by your nameservers OK. All nameservers returned by the parent server nsb.nic.uk are the same as the ones reported by your nameservers.
Pass Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Pass NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Warn Different subnets WARNING: Not all of your nameservers are in different subnets
Pass IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
Pass DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
Warn Different autonomous systems WARNING: Single point of failure
Pass Stealth NS records sent Ok. No stealth ns records are sent
SOA Info SOA recordThe SOA record is:
Primary nameserver: ns1.blogdir.co.uk
Hostmaster E-mail address: admin.blogdir.co.uk
Serial #: 30
Refresh: 604800
Retry: 86400
Expire: 2419200   4 weeks
Default TTL: 604800
Pass NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 30.
Pass SOA MNAME entry OK. ns1.blogdir.co.uk That server is listed at the parent servers.
Pass SOA Serial Your SOA serial number is: 30. The recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision.
Your SOA serial appears to be the number of seconds since midnight 01 Jan 1970 when the last DNS change was made. That seems to be 1969/12/31 18:0:30
Warn SOA REFRESH WARNING: Your SOA REFRESH interval is: 604800. That is not so ok
Warn SOA RETRY Your SOA RETRY value is: 86400. That is NOT OK
Pass SOA EXPIRE Your SOA EXPIRE number is: 2419200.Looks ok
Warn SOA MINIMUM TTL Your SOA MINIMUM TTL value is: 604800. This value seems a little high. You should consider decreasing this value to about 1-3 hours as recommanded by RFC2308. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a value of 1-3 hours.
MX Error MX RecordsOh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!
WWW Info WWW A Record Your www.blogdir.co.uk A record is:
www.blogdir.co.uk  [51.89.145.76] 
Pass IPs are public OK. All of your WWW IPs appear to be public IPs.
Pass WWW CNAME OK. No CNAME

Processed in 9.064 seconds.