https://viewdns.info/dnsreport/?domain=mynetname.net
FAILEDSame NS records at each local nameserverOops! Your name servers don't all seem to have identical NS records for your domain. This could lead to some visitors not being able to see your site (or seeing it on a different server)! This should be fixed ASAP!
-----------
FAILEDLocal nameservers answer authoritativelyOops! The following nameservers do not answer authoritatively for your domain:
ns1.kissthenet.net.
This means that these servers don't have a zone file for your domain and are simply looking up the details themselves! This is not a good thing!
-----------
FAILEDNo CNAME records for nameserversOops! One or more CNAME records are present for your nameservers. RFC1912 section 2.4 and RFC2181 section 10.3 state that there should be no CNAME records if any other records are present for a nameserver. This is due to the fact that having a CNAME (essentially a redirect) and any other record (explicit values) will cause confusion over which takes priority.
-----------
FAILEDNameservers allow TCP connectionsOops! We couldn't connect to the following nameservers using TCP on port 53:
ns2.kissthenet.net.
ns1.kissthenet.net.
-----------
WARNINGSOA Refresh valueOops! Your SOA Refresh value (60) is outside of the recommended range of 1 hour (3600) to 1 day (86400). This value basically means 'how long can the secondary nameserver have out of date information after updating the primary nameserver?' and should be within the recommended range.
These are minor
FAILEDAll nameservers have same SOA serial numberOops! It seems your nameservers don't agree on the SOA serial number! This probably means that changes made on one nameserver weren't made on another. This could lead to intermittent connectivity issues and should be fixed ASAP.
-----------
WARNINGSOA serial number formatOops! Your SOA serial number (1703753349) doesn't seem to be in the recommended format (YYYYMMDDnn - where nn is the revision number). This is still OK, however as long as you are keeping track of your SOA version details.
-----------
Apparently the intern setup DNS...can we have a professional here?
FAILEDSame NS records at each local nameserverOops! Your name servers don't all seem to have identical NS records for your domain. This could lead to some visitors not being able to see your site (or seeing it on a different server)! This should be fixed ASAP!
-----------
FAILEDLocal nameservers answer authoritativelyOops! The following nameservers do not answer authoritatively for your domain:
ns1.kissthenet.net.
This means that these servers don't have a zone file for your domain and are simply looking up the details themselves! This is not a good thing!
-----------
FAILEDNo CNAME records for nameserversOops! One or more CNAME records are present for your nameservers. RFC1912 section 2.4 and RFC2181 section 10.3 state that there should be no CNAME records if any other records are present for a nameserver. This is due to the fact that having a CNAME (essentially a redirect) and any other record (explicit values) will cause confusion over which takes priority.
-----------
FAILEDNameservers allow TCP connectionsOops! We couldn't connect to the following nameservers using TCP on port 53:
ns2.kissthenet.net.
ns1.kissthenet.net.
-----------
WARNINGSOA Refresh valueOops! Your SOA Refresh value (60) is outside of the recommended range of 1 hour (3600) to 1 day (86400). This value basically means 'how long can the secondary nameserver have out of date information after updating the primary nameserver?' and should be within the recommended range.
These are minor
FAILEDAll nameservers have same SOA serial numberOops! It seems your nameservers don't agree on the SOA serial number! This probably means that changes made on one nameserver weren't made on another. This could lead to intermittent connectivity issues and should be fixed ASAP.
-----------
WARNINGSOA serial number formatOops! Your SOA serial number (1703753349) doesn't seem to be in the recommended format (YYYYMMDDnn - where nn is the revision number). This is still OK, however as long as you are keeping track of your SOA version details.
-----------
Apparently the intern setup DNS...can we have a professional here?
Statistics: Posted by silversword — Thu Dec 28, 2023 10:57 am