Category | Status | Test name | Information send feedback |
---|---|---|---|
Parent | Domain NS records | Nameserver records returned by the parent servers are: f1g1ns1.dnspod.net. ['117.89.178.173', '36.155.149.233', '1.12.0.4', '163.177.5.23', '112.80.181.45', '120.241.130.22', '129.211.176.209', '125.94.59.210'] (NO GLUE) [TTL=172800] f1g1ns2.dnspod.net. ['112.80.181.111', '120.241.130.98', '129.211.176.239', '163.177.5.47', '36.155.149.176', '117.89.178.184', '1.12.0.1'] (NO GLUE) [TTL=172800] 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 | The parent nameserver e.gtld-servers.net is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happens a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.) | ||
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: Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly. |
|
Recursive Queries | Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone. | ||
Same Glue | Hmm,I do not consider this to be an error yet, since I did not detect any nameservers at your nameservers. | ||
Glue for NS records | OK. Your nameservers (the ones reported by the parent server) have no ideea who your nameservers are so this will be a pass since you already have a lot of errors! | ||
Mismatched NS records | WARNING: One or more of your nameservers did not return any of your NS records. | ||
DNS servers responded | Good. All nameservers listed at the parent server responded. | ||
Name of nameservers are valid | OK. The nameservers reported by the parent send out nothing as shown above. I can't check nothing so it's a green! | ||
Multiple Nameservers | ERROR: Looks like you have less than 2 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 | You should already know that your NS records at your nameservers are missing, so here it is again:
f1g1ns1.dnspod.net. f1g1ns2.dnspod.net. |
||
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: f1g1ns1.dnspod.net Hostmaster E-mail address: freednsadmin.dnspod.com Serial #: 1635128801 Refresh: 3600 Retry: 180 Expire: 1209600 2 weeks Default TTL: 180 |
|
NSs have same SOA serial | OK. All your nameservers agree that your SOA serial number is 1635128801. | ||
SOA MNAME entry | OK. f1g1ns1.dnspod.net That server is listed at the parent servers. | ||
SOA Serial | Your SOA serial number is: 1635128801. This can be ok if you know what you are doing. | ||
SOA REFRESH | OK. Your SOA REFRESH interval is: 3600. That is OK | ||
SOA RETRY | Your SOA RETRY value is: 180. Looks ok | ||
SOA EXPIRE | Your SOA EXPIRE number is: 1209600.Looks ok | ||
SOA MINIMUM TTL | Your SOA MINIMUM TTL is: 180. 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 180 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.fxlydz.com A record is: www.fxlydz.com [40.83.124.209] |
|
IPs are public | OK. All of your WWW IPs appear to be public IPs. | ||
WWW CNAME | OK. No CNAME |
Processed in 1.296 seconds.