Archived and Closed
This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: • We have archived this topic as it has either reached a resolution or has become inactive. If you believe this topic should not have been archived, please let us know, and we would be happy to review it. You may continue to access this topic as needed
I've performed a domain health check and the following information was pointed out:
1) Your nameserver do not include A records when asked for your NS records.
1a.) Your DNS servers when asked for www.wedtin.com. return the following records:
2) Your nameservers are on the same Class C IP range. This is very bad if you want to be found in the case of outage, or even worst, problems!
3) I have searched for differing IPs for your MX records between what are declaring your NS and the authoritative NS for the MX records. The check failed because.
4) Your SOA serial number is 1619664802. It doesn't appear to be in therecommended format of YYYYMMDDnn, you should change it accordingly. Your SOA serial number is 1619664802. It doesn't appear to be in therecommended format of YYYYMMDDnn, you should change it accordingly.
5) There is one or more CNAMEs record pointing to www.wedtin.com.. This can cause extra bandwidth usage since the resolution of www.wedtin.com. is done in multiple steps. However this is only a warning!
6)Not all of your mailservers accept mail from "<>". RFC1123 5.2.9 requires all mailservers to receive mail from this kind of address, which is used in reject/bounce messages and return receipts. The report of the test is: mx.wedtin.com.: Does not accept null sender