Processed in 0.392 seconds.
|Parent||Domain NS records||Nameserver records returned by the parent servers are:|
ns77.domaincontrol.com. ['188.8.131.52'] (NO GLUE) [TTL=86400]
ns78.domaincontrol.com. ['184.108.40.206'] (NO GLUE) [TTL=86400]
b2.org.afilias-nst.org was kind enough to give us that information.
|TLD Parent Check||Good. b2.org.afilias-nst.org, 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 b2.org.afilias-nst.org 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 b2.org.afilias-nst.org 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:
ns78.domaincontrol.com ['220.127.116.11'] [TTL=3600]
ns77.domaincontrol.com ['18.104.22.168'] [TTL=3600]
|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:
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 b2.org.afilias-nst.org 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: ns77.domaincontrol.com
Hostmaster E-mail address: dns.jomax.net
Serial #: 2018080404
Expire: 604800 1 weeks
Default TTL: 600
|NSs have same SOA serial||OK. All your nameservers agree that your SOA serial number is 2018080404.|
|SOA MNAME entry||OK. ns77.domaincontrol.com That server is listed at the parent servers.|
|SOA Serial||Your SOA serial number is: 2018080404. This appears to be in the recommended format of YYYYMMDDnn.|
|SOA REFRESH||OK. Your SOA REFRESH interval is: 28800. That is OK|
|SOA RETRY||Your SOA RETRY value is: 7200. Looks ok|
|SOA EXPIRE||Your SOA EXPIRE number is: 604800.Looks ok|
|SOA MINIMUM TTL||Your SOA MINIMUM TTL is: 600. 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 600 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||ERROR: I could not get any A records for www.vintagebigblue.org!
(I only do a cache request, if you recently added a WWW A record, it might not show up here.)
The last changes I made to my DNS records was over 52 hours ago.
Any help would be appreciated.