| Test Result | Analysis | |
|---|---|---|
| Fail |
Check nameservers at parent
The following nameserver(s) are missing at the parent 'auth-ns1.ucd.ie.': Recommendation Contact your registrar to add the missing nameservers to the parent, and be sure to include all available nameservers in your domain's delegation. |
|
| Info |
Check nameserver glue records from parent
The following nameserver(s) are missing glue records at the parent 'auth-ns1.ucd.ie.': Recommendation If your domain is a different TLD than its nameservers (for example, domain.com delegated to ns1.domain.org and ns2.domain.net), the parent will lack glue records. This is perfectly normal. If your domain and its nameservers are in the same TLD, and you are seeing this message, contact your registrar to add glue records for your nameservers to the parent. |
|
| Pass |
Check glue record matching
All of your glue records match those returned from your nameservers. |
|
| Fail |
Check the number of nameservers
Parent reported only one nameserver for your domain. Recommendation Contact your registrar to add at least one additional nameserver. With only a single point of failure, your domain risks losing resolution entirely if an outage occurs at your single nameserver. |
| Test Result | Analysis | |
|---|---|---|
| Pass |
Check for public nameserver IP addresses
The IP addresses of your nameservers are publicly available from any TCP/IP network. |
|
| Pass |
Check the nameserver FQDN validity
All nameservers reported by the parent have valid hostnames. |
|
| Fail |
Check for A records corresponding to NS records
The following NS records do not have A records returned: |
|
| Pass |
Check for identical nameserver responses
This test passes, but please note that you have only one set of NS records. |
|
| Pass |
Check for nameserver response
All nameservers responded to at least one query about your domain. |
|
| Fail |
Check for lame nameservers
The following nameservers are delegated by the parent but do not respond authoritatively: Recommendation Contact the hostmaster for your nameservers to have the nameserver respond authoritatively for your domain. |
|
| Fail |
Check for stealth nameservers
Some of your nameservers returned NS records that are missing from the parent nameserver: Recommendation There are more nameservers available for your domain than you are currently using (e.g. four out of five). Contact your registrar and delegate your domain to all of the available authoritative nameservers. |
|
| Pass |
Check for missing nameservers
Your nameservers are not missing any NS records. |
|
| Fail |
Check separate nameserver networks
Parent provided only one nameserver for your domain. Recommendation You need at least two nameservers in separate class C networks. |
|
| Pass |
Check for CNAME records for nameservers
You do not have CNAME records for nameserver hostnames in your zone. |
|
| Info |
Check for nameserver DNS server versions
Your nameservers appear to be using the following software to serve DNS queries: |
|
| Warning |
Check for open recursive DNS
Following nameservers answered recursive DNS queries: Recommendation Do not use open recursive as nameserver for your zones. |
|
| Pass |
Check for open zone transfers
Your nameservers do not allow zone transfers. |
| Test Result | Analysis | |
|---|---|---|
| Fail |
Check SOA record
We cannot find any SOA record returned from your nameservers. Recommendation Make sure that your zone is loaded on the DNS servers listed for your domain, and that the nameservers you are using are authoritative for your domain. |
|
| Fail |
Check SOA MNAME
We don't have SOA data to analyze. |
|
| Fail |
Check SOA RNAME
We don't have SOA data to analyze. |
|
| Fail |
Check SOA serial
We don't have SOA data to analyze. |
|
| Fail |
Check SOA refresh
We don't have SOA data to analyze. |
|
| Fail |
Check SOA retry
We don't have SOA data to analyze. |
|
| Fail |
Check SOA expiration
We don't have SOA data to analyze. |
|
| Fail |
Check SOA MINTTL
We don't have SOA data to analyze. |
| Test Result | Analysis | |
|---|---|---|
| Warning |
Check RRSIG validity for all important DNS resource records
Your nameservers do not provide DNSSEC information with their answers. |
| Test Result | Analysis | |
|---|---|---|
| Warning |
Check the number of MX hosts
Your nameservers report only one unique MX record. We recommend having more than one in order to ensure reliable mail delivery. Recommendation You should consider including a secondary mail server to handle your mail if the primary server fails. |
|
| Pass |
Check MX records for Public IPs
All MX records resolve to public IPs. |
|
| Pass |
Check for valid MX records with unique IP address
Your MX records resolve to unique hostnames with an A record pointing to unique IP addresses. |
|
| Info |
Check for Mailexchanger IPs reverse DNS records
The following mailexchangers IP do not have reverse DNS: Recommendation It's recommended for your mailservers to have reverse DNS if they connect to other MTA to transport mail. |
|
| Pass |
Check that all MX returned are valid hostnames
Your nameservers return MX records pointing to valid FQDNs. |
|
| Info |
Check for open relay mail servers
The following mail servers were not tested for open relay service: |
|
| Pass |
Check for port 25 connection
All of your mail servers accept TCP connections. |
|
| Pass |
Check for port 465 connection
All of your mail servers accept TCP connections. |
|
| Fail |
Check for mail server banners
The following mail servers did not display a banner: Recommendation Configure your mail server to display a banner upon connection. |
|
| Fail |
Check to see if mail server accepts mail from empty address
The following mailexchangers did not accept mail from empty sender address Recommendation Your mailexchanger needs to accept mail for according to RFC822. |
|
| Fail |
Check to see if mail server accepts mail to postmaster@
The following mailexchangers did not accept mail for postmaster Recommendation Your mailexchanger needs to accept mail for according to RFC822. |
|
| Fail |
Check to see if mail server accepts mail to abuse@
The following mailexchangers did not accept mail for abuse alias Recommendation Your mailexchanger needs to accept mail for according to RFC822. |
|
| Warning |
Check SPF record
You don't have any SPF resource records in your DNS zone. Recommendation You should create a SPF record for your DNS zone. This will help prevent e-mails being sent from your domain that are forged. If you need assistance with how to format a valid SPF record, please use the SPF Wizard (http://old.openspf.org/wizard.html). |
source.cdi.ul.ie. 3600 IN A 193.1.101.122 cdi.ul.ie. 3600 IN NS source.cdi.ul.ie.
cdi.ul.ie. 14400 IN A 193.1.101.58 cdi.ul.ie. 86400 IN NS source.cdi.ul.ie. cdi.ul.ie. 86400 IN NS mercury.ul.ie. cdi.ul.ie. 14400 IN MX 0 cdi.ul.ie.
cdi.ul.ie. 14400 IN A 193.1.101.58 cdi.ul.ie. 14400 IN NS mercury.ul.ie. cdi.ul.ie. 14400 IN NS source.cdi.ul.ie. cdi.ul.ie. 14400 IN MX 0 cdi.ul.ie.
mercury.ul.ie. 3599 IN A 193.1.100.130 cdi.ul.ie. 14400 IN A 193.1.101.58
ip: 193.1.101.122 tcp: 1 axfr: 0 fpdns: ISC BIND 9.2.3rc1 -- 9.4.0a0 recursion: 0 version.bind: 9.3.6-P1-RedHat-9.3.6-4.P1.el5 asn: 1213 response_time: 106 ms
ip: 193.1.100.130 tcp: 1 axfr: 0 fpdns: TIMEOUT recursion: 1 asn: 1213 response_time: 106.2 ms
193.1.101.58 tcp_connect: "1" 193.1.101.58 PTR: "" 193.1.101.58 ssl_connect: "0"