Torrent Reactor is one of them as, apart from including plenty of contents, it works very well and its design makes it really easy to use. All of your There are loads out there, but very few of them are really worth it. You have reverse (PTR) records for all your IPs, that is a good thing. I have not found duplicate IP(s) for your MX records. I did not detect differing IPs for your MX records. You should be careful about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time. Looks like you only have one MX record at your nameservers. No CNAMEs returned for A records lookups.
All of your MX records appear to use public IPs. I did not detect any invalid hostnames for your MX records. This tests to see if there areĪny MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs Looks like all your nameservers have the same set of MX records. Your MX records that were reported by your nameservers are: 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Ĭache the negative answer). Your SOA EXPIRE number is: 604800.Looks ok This appears to be in the recommended format of YYYYMMDDnn. WARNING: SOA MNAME ( ) is not listed as a primary nameserver at your parent nameserver!
#TORRENTREACTOR TO SERIAL NUMBER#
All your nameservers agree that your SOA serial number is 2022031701. This is a good thing and useful even if UDP connections are used by default. Seems all your DNS servers allow TCP connections. This is a good thing because it will prevent DNS delays and other problems like Looks like the IP addresses of your nameservers are public. WARNING: Not all of your nameservers are in different subnets RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. 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). Missing nameservers reported by your nameserversĮRROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. You need to make sure that these nameservers are working.If they are not working ok, you may have problems! All the nameservers listed at the parent servers answer authoritatively for your domain.įAIL: 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). According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. All of the NS records that your nameservers report seem valid. All nameservers listed at the parent server responded. The NS records at all your nameservers are identical. This is a good thing as it will spare an extra A lookup needed to find those A records. When I asked your nameservers for your NS records they also returned the A records for the NS records. If there are any missing or stealth nameservers you should see them below! This tests only nameservers that are common at the parent and at 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. The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. It may be that I am wrong but the chances of that are low. I could use the nameservers listed below to performe recursive queries. NS records got from your nameservers listed at the parent NS are: This happens a lot if you have nameservers on different TLD ( for example with nameserver ns.) 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.
The parent nameserver 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. 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. The parent server has your nameservers listed. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check. Good. , the parent server I interrogated, has information for your TLD. was kind enough to give us that information. Nameserver records returned by the parent servers are:
0 kommentar(er)
