I have some major mail problems on my dedicated server.
I'll put my dnsreport.com report here:
FAIL Duplicate MX records WARNING:
You only have duplicate MX records. This means that mailservers may try delivering mail to the same IP more than once. Although technically valid, this is very confusing, and wastes resources. The duplicate MX records are:
66.90.xx.n2.mydomain.net. and 66.90.xx.n1.mydomain.net. both resolve to 0.0.0.0.
FAIL Reverse DNS entries for MX records ERROR: None of your mail server(s) seem to have reverse DNS (PTR) entries (I didn't get any responses for them). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry.
FAIL Connect to mail servers ERROR: I could not complete a connection to any of your mailservers!
66.90.xx.n2.mydomain.net: Could not connect without glue or A record.
66.90.xx.n1.mydomain.net: Could not connect without glue or A record.
If this is a timeout problem, note that the DNS report only waits about 30 seconds for responses, so your mail may work fine in this case but you will need to use testing tools specifically designed for such situations.
The reverse DNS is set and the IPs are delecated to my server.
I'm using Webmin to manage the server but I don't seem to get this thing going.
Your MX records are screwed up. It looks like you used IP addresses and didn't include a trailing period. Use a hostname with its own A record (like mail.yourdomain.net) and put a period on the end of it so BIND doesn't append your domain name to it.
Your MX records should both have names of "mydomain.net.", not ns1 and ns2.mydomain.net. You also need to delete the two MX records that currently exist for mydomain.net that list IP addresses as the mail servers.
The change helped to get rid of those messages tnx
but now I get a message about revers DNS:
FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site. The problem MX records are:
n1.xx.90.66.in-addr.arpa [No reverse DNS entry (rcode: 2 ancount: 0)]
n2.xx.90.66.in-addr.arpa [No reverse DNS entry (rcode: 2 ancount: 0)]