DNS records

Category	Test name	Information send feedback
Parent	Domain NS records	Nameserver records returned by the parent servers are: // e.gtld-servers.net was kind enough to give us that information.
	TLD Parent Check	Good. e.gtld-servers.net, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like “co.us” for example that are missing a direct check.
	Your nameservers are listed	Good. The parent server e.gtld-servers.net 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.
	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)
	Nameservers A records	Good. Every nameserver listed has A records. This is a must if you want to be found.
NS	NS records from your nameservers	NS records got from your nameservers listed at the parent NS are: //
	Recursive Queries	Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
	Same Glue	The A records (the GLUE) got from the parent zone check are the same as 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 according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below!
	Glue for NS records	INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are: // 123.45.67.890 // 123.45.67.891 You can fix this for example by adding A records to your nameservers for the zones listed above.
	Mismatched NS records	OK. The NS records at all your nameservers are identical.
	DNS servers responded	Good. All nameservers listed at the parent server responded.
	Name of nameservers are valid	OK. All of the NS records that your nameservers report seem valid.
	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.
	Nameservers are lame	OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
	Missing nameservers reported by parent	OK. All NS records are the same at the parent and at your nameservers.
	Missing nameservers reported by your nameservers	OK. All nameservers returned by the parent server e.gtld-servers.net are the same as the ones reported by your nameservers.
	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.
	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.
	Different subnets	OK. Looks like you have nameservers on different subnets!
	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
	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.
	Different autonomous systems	OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
	Stealth NS records sent	Ok. No stealth ns records are sent
SOA	SOA record	The SOA record is: Primary nameserver: // grannbo.ns.cloudflare.com Hostmaster E-mail address: // dns.cloudflare.com Serial #: // 123456789 Refresh: // 10000 Retry: // 2400 Expire: // 604800 1 weeks Default TTL: // 3600
	NSs have same SOA serial	OK. All your nameservers agree that your SOA serial number is // 123456789.
	SOA MNAME entry	OK. // grannbo.ns.cloudflare.com That server is listed at the parent servers.
	SOA Serial	Your SOA serial number is: // 123456789. This can be ok if you know what you are doing.
	SOA REFRESH	OK. Your SOA REFRESH interval is: // 10000. That is OK
	SOA RETRY	Your SOA RETRY value is: // 2400. Looks ok
	SOA EXPIRE	Your SOA EXPIRE number is: // 604800.Looks ok
	SOA MINIMUM TTL	Your SOA MINIMUM TTL is: // 3600. 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. Your value of // 3600 is OK.
MX	MX Records	Your MX records that were reported by your nameservers are: 1 aspmx.l.google.com 123.45.67.890 (no glue) 5 alt1.aspmx.l.google.com 123.45.67.890 (no glue) 5 alt2.aspmx.l.google.com 123.45.67.890 (no glue) 10 alt3.aspmx.l.google.com 123.45.67.890 (no glue) 10 alt4.aspmx.l.google.com 123.45.67.890 (no glue) [These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
	Different MX records at nameservers	Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
	MX name validity	Good. I did not detect any invalid hostnames for your MX records.
	MX IPs are public	OK. All of your MX records appear to use public IPs.
	MX CNAME Check	OK. No problems here.
	MX A request returns CNAME	OK. No CNAMEs returned for A records lookups.
	MX is not IP	OK. All of your MX records are host names.
	Number of MX records	Good. Looks like you have multiple MX records at all your nameservers. This is a good thing and will help in preventing loss of mail.
	Mismatched MX A	OK. I did not detect differing IPs for your MX records.
	Duplicate MX A records	OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
	Reverse MX A records (PTR)	Your reverse (PTR) record: 98.7.654.321.in-addr.arpa -> rc-in-f26.1e100.net 98.7.654.321.in-addr.arpa -> wq-in-f26.1e100.net 98.7.654.321.in-addr.arpa -> ta-in-f26.1e100.net 98.7.654.321.in-addr.arpa -> sa-in-f26.1e100.net 98.7.654.321.in-addr.arpa -> la-in-f27.1e100.net You have reverse (PTR) records for all your IPs, that is a good thing.
WWW	WWW A Record	Your www.ajsrp.com A record is: // www.domain.com [104.26.5.40] [172.67.72.134] [104.26.4.40]
	IPs are public	OK. All of your WWW IPs appear to be public IPs.
	WWW CNAME	OK. No CNAME

A record

Maps a name to IP addresses.

CNAME record

Maps a name to another name. It should only be used when there are no other records on that name.

ALIAS record

Maps a name to another name, but can coexist with other records on that name.

URL record

Redirects the name to the target name using the HTTP 301 status code.

The A, CNAME, and ALIAS records cause a name to resolve to an IP. Conversely, the URL record redirects the name to a destination. The URL record is a simple and effective way to apply a redirect for one name to another name, for example redirecting www.example.com to example.com.
The A name must resolve to an IP. The CNAME and ALIAS records must point to a name.
Never use a CNAME record for your root domain name (e.g. example.com).

MX Record

Mail Exchanger (MX), similar to A name records but entirely devoted to sending and receiving e-mail.

CERT

CERT records store site certificates as part of the DNS information.

NAPTR Records

A rare record type that’s used to map telephone numbers and e-mail addresses for VoIP and SIP servers.

PTR Record

PTR directs IP traffic to domains.

TXT Record

TXT is used commonly to verifying domain ownership. It holds data sender policy framework (SPF) .

intoDNS

Understanding DNS records – A, CNAME, ALIAS, URL, MX, CERT, NAPTR, PTR, TXT