*

category Status test name details send feedback
Parent Domain NS records Nameserver documents returned by the parental servers are: ns1.parkingcrew.net. <'13.248.158.159'>(NO GLUE) ns2.parkingcrew.net. <'76.223.21.9'>(NO GLUE) a.dns.ws was kind sufficient to give us the information.

*
*

TLD parent Check Good.a.dns.ws, the parental server i interrogated, has actually information for her TLD. This is a great thing together there room some other domain extensions like "co.us" for example that are lacking a direct check.
Your nameservers are listed Good. The parental server a.dns.ws has actually your nameservers listed. This is a have to if you want to be found as anyone the does not recognize your DNS servers will first ask the parent nameservers.

You are watching: ]]]]]]]]]]]]onlyfilms.ws

DNS Parent sent out Glue The parental nameserver a.dns.ws is not sending out out GLUE for every nameservers listed, definition he is sending out her nameservers host names without sending out the A documents of those nameservers. It"s ok yet you need to know that this will call for an extra A lookup that can delay a tiny the relations to your site. This happens a lot of if you have nameservers on different TLD (domain.com for instance with nameserver ns.domain.org.)
Nameservers A records Good. Every nameserver noted has A records. This is a must if you desire to be found.
NS NS documents from her nameserversNS records obtained from her nameservers listed at the parent NS are: ns1.parkingcrew.net<'13.248.158.159'> ns2.parkingcrew.net<'76.223.21.9'>
*
Recursive Queries I might use the nameservers noted below to performe recursive queries. It might be that i am wrong yet the chances of that space low. You must not have nameservers that enable recursive queries together this will allow almost anyone to usage your nameservers and can reason problems. Difficulty record(s) are: 13.248.158.159 76.223.21.9
Same Glue The A documents (the GLUE) obtained from the parental zone check are the same as the ones got from your nameservers. You have to make certain your parental server has the same NS documents for your zone together you perform according to the RFC. This tests only nameservers the are common at the parent and also at your nameservers. If there are any missing or stealth nameservers you have to see them below!
Glue because that NS records INFO: adhesive was no sent once I asked your nameservers for your NS records.This is ok but you should understand that in this situation an extra A document lookup is forced in bespeak to get the IPs of your NS records. The nameservers there is no glue are: 13.248.158.159 76.223.21.9You deserve to fix this for instance by adding A documents to your nameservers because that the zones provided above.
Mismatched NS records OK. The NS documents at all your nameservers space identical.
DNS servers responded Good. Every nameservers listed at the parent server responded.
Name of nameservers space valid OK. All of the NS records that her nameservers report seem valid.
Multiple Nameservers Good. You have actually multiple nameservers. According to RFC2182 ar 5 you must have actually at least 3 nameservers, and also no much more than 7. Having actually 2 nameservers is also ok by me.
Nameservers space lame OK. All the nameservers detailed at the parent servers prize authoritatively for your domain.
Missing nameservers reported by parent OK. Every NS records are the same at the parent and also at her nameservers.
Missing nameservers report by your nameservers OK. Every nameservers went back by the parental server a.dns.ws space the same as the ones report by your nameservers.
Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state the there must be no CNAMEs if an NS (or any kind of other) document is present.
NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state the there have to be no CNAMEs if an NS (or any other) record is present.
Different subnets OK. Looks choose you have nameservers on different subnets!
IPs that nameservers are public Ok. Looks like the IP addresses of your nameservers room public. This is a great thing because it will stop DNS delays and other problems like
DNS servers enable TCP connection OK. Appears all her DNS servers allow TCP connections. This is a an excellent thing and also useful even if UDP connections are provided by default.
Different autonomous systems OK. It appears you are safe indigenous a single point of failure. You should be careful about this and try to have nameservers on various locations together it have the right to prevent a lot of of troubles if one nameserver walk down.
Stealth NS documents sent Ok. No stealth ns documents are sent
SOA SOA recordThe SOA record is: major nameserver: ns1.parkingcrew.net Hostmaster E-mail address: hostmaster.onlyfilms.ws Serial #: 1634109000 Refresh: 28800 Retry: 7200 Expire: 604800 1 weeks Default TTL: 86400
NSs have same SOA serial OK. All your nameservers agree the your SOA serial number is 1634109000.
SOA MNAME entry OK. ns1.parkingcrew.net that server is noted at the parent servers.
*
SOA Serial Your SOA serial number is: 1634109000. This have the right to be ok if you know what you space doing.
SOA REFRESH OK. Her SOA refresh interval is: 28800. The is OK
SOA RETRY Your SOA RETRY value is: 7200. Watch ok
SOA EXPIRE Your SOA EXPIRE number is: 604800.Looks ok
SOA MINIMUM TTL Your SOA MINIMUM TTL is: 86400. This value was used to serve as a default TTL for records without a provided TTL value and now is used for an unfavorable caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a worth of 1-3 hours. Your value of 86400 is OK.

See more: How Long Does It Take For Asphalt To Dry ? How Long Until You Can Drive On New Asphalt

MX
*
MX RecordsOh well, ns did not detect any kind of MX documents so you most likely don"t have any and if you understand you should have then they might be lacking at her nameservers!
WWW WWW A Record your www.onlyfilms.ws A record is: www.onlyfilms.ws <185.53.178.51>
IPs are public OK. Every one of your WWW IPs show up to be public IPs.
WWW CNAME OK. No CNAME

Processed in 0.419 seconds.