Results 1 to 12 of 12
  1. #1
    Join Date
    Dec 2003
    Location
    Toronto, Ontario
    Posts
    26

    Mail problems :(

    Hello!

    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.

    Any help is greatly appreciated!!!

  2. #2
    Join Date
    Jun 2003
    Posts
    673
    What's your domain name?

  3. #3
    Join Date
    Jun 2003
    Posts
    673
    Are your .83 and .91 DNS servers both down? I don't get any response when pinging them, and they don't answer DNS queries about your domain for me.

  4. #4
    Join Date
    Dec 2003
    Location
    Toronto, Ontario
    Posts
    26
    da*n, the whole subnet seems to be down

  5. #5
    Join Date
    Dec 2003
    Location
    Toronto, Ontario
    Posts
    26
    anyone?

  6. #6
    Join Date
    Jun 2003
    Posts
    673
    What do you want us to do? Call your ISP and complain about the network being down? :)

  7. #7
    Join Date
    Dec 2003
    Location
    Toronto, Ontario
    Posts
    26
    oh no, the network got up the same day. they had the router damaged by an electrical surge - or so they said

  8. #8
    Join Date
    Jun 2003
    Posts
    673
    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.

  9. #9
    Join Date
    Dec 2003
    Location
    Toronto, Ontario
    Posts
    26
    This is a bit confusing

    I currently have 2 A records:

    1st:
    Name: ns1.mydomain.net
    Address: 66.90.xx.n1
    TTL: Default

    2nd:
    Name: ns2.mydomain.net
    Address: 66.90.xx.n2
    TTL: Default

    and 2 MX records:

    1st:
    Name: ns1.mydomain.net.
    TTL: Default
    Priority: 1
    Mail server: ns1.mydomain.net.

    2nd:
    Name: ns2.mydomain.net.
    TTL: Default
    Priority: 2
    Mail server: ns2.mydomain.net.

    what has to be changed?

    Thanks again for your help!

  10. #10
    Join Date
    Jun 2003
    Posts
    673
    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.

  11. #11
    Join Date
    Dec 2003
    Location
    Toronto, Ontario
    Posts
    26
    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)]

    I have the following DNS records:

    Address: 66.90.xx.n1.mydomain.net.
    hostname: ns1.mydomain.net.

    and

    Address: 66.90.xx.n2.mydomain.net.
    hostname: ns2.mydomain.net.

    Thanks a bunch again!

  12. #12
    Join Date
    Jun 2003
    Posts
    673

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •