|Category||Status||Test name||Information send feedback|
|Parent||Domain NS records||Nameserver records returned by the parent servers are:|
ns1hnx.name.com. ['18.104.22.168'] [TTL=172800]
ns2kry.name.com. ['22.214.171.124'] [TTL=172800]
ns3dkz.name.com. ['126.96.36.199'] [TTL=172800]
ns4kmw.name.com. ['188.8.131.52'] [TTL=172800]
d.gtld-servers.net was kind enough to give us that information.
|TLD Parent Check||Good. d.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 d.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:
ns3.name.com ['184.108.40.206'] [TTL=300]
ns2.name.com ['220.127.116.11'] [TTL=300]
ns4.name.com ['18.104.22.168'] [TTL=300]
ns1.name.com ['22.214.171.124'] [TTL=300]
|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||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.|
|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||FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!
|Missing nameservers reported by your nameservers||ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).
|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: ns1.name.com
Hostmaster E-mail address: support.name.com
Serial #: 1
Expire: 604800 1 weeks
Default TTL: 300
|NSs have same SOA serial||OK. All your nameservers agree that your SOA serial number is 1.|
|SOA MNAME entry||WARNING: SOA MNAME (ns1.name.com) is not listed as a primary nameserver at your parent nameserver!|
|SOA Serial||Your SOA serial number is: 1.
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:1
|SOA REFRESH||OK. Your SOA REFRESH interval is: 10800. That is OK|
|SOA RETRY||Your SOA RETRY value is: 3600. Looks ok|
|SOA EXPIRE||Your SOA EXPIRE number is: 604800.Looks ok|
|SOA MINIMUM TTL||Your SOA MINIMUM TTL is: 300. 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 300 is OK.|
|MX||MX Records||Oh 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||WWW A Record||
Your www.sweetwap.com A record is:
|IPs are public||OK. All of your WWW IPs appear to be public IPs.|
|WWW CNAME||OK. No CNAME|
Processed in 0.601 seconds.