Skip to main content

Cannot receive email on specific domain

Comments

10 comments

  • quanin
    That definitely sounds like a DNS issue. Can you do two things, right quick? From the server: ping -c4 domain.com From your local machine: ping domain.com Somebody somewhere isn't getting the message that your domain exists. This will rule out the possibility of it being a wider issue than your server.
    0
  • sepisepsep
    That definitely sounds like a DNS issue. Can you do two things, right quick? From the server: ping -c4 domain.com From your local machine: ping domain.com Somebody somewhere isn't getting the message that your domain exists. This will rule out the possibility of it being a wider issue than your server.

    yes no issues there. The server itself is hosting the domain.com. Even system email messages are failing.
    0
  • quanin
    Understood. I was attempting to verify if it's only exim that's failing to resolve that particular domain, as that would be a slightly easier issue to fix than if it was a larger issue. Are you saying you can ping that domain from both server and local machine?
    0
  • sepisepsep
    Understood. I was attempting to verify if it's only exim that's failing to resolve that particular domain, as that would be a slightly easier issue to fix than if it was a larger issue. Are you saying you can ping that domain from both server and local machine?

    Yes, I can ping it on from both. Not really seeing any connectivity issues.
    0
  • quanin
    It may be then that you need to rebuild /etc/localdomains. As root, do: /scripts/checkalldomainsmxs "yes
    0
  • sepisepsep
    It may be then that you need to rebuild /etc/localdomains. As root, do: /scripts/checkalldomainsmxs "yes

    Was already able to fix it. Issue was even after updating DNS records through cPanel account, the domain was still listed on /etc/remotedomains and NOT on the /etc/localdomains . I think this might be a bug as I suppose it should've been automatic once I've pointed the MX record to the server's domain. I resolved the issue by simply entering the Edit DNS Zone section through WHM and saving the config just to initialize the script to update. And true enough, after saving it, the domain has been transferred to /etc/localdomains. Markers that helped me to identify issue are below. Error message on tracking email delivery: Router: fail_remote_domains
    Exim log:2019-02-19 08:35:43 1gvtNv-0017q0-OK ** cpanel@domain.com R=fail_remote_domains: The mail server could not deliver mail to cpanel@domain.com. The account or domain may not exist, they may be blacklisted, or missing the proper dns entries.
    The fail_remote_domains apparently mentioned that it's seeing the domain to be remote and NOT local. Thanks for your helpful inputs, quanin.
    0
  • quanin
    Any time. I think editing the DNS zone runs the above script just for that domain anyway, so you essentially just did the same thing. You may want to open a support ticket and reference this thread, in the event your theory's correct and it's a bug. The devs may be interested in taking a closer look.
    0
  • cPanelMichael
    Hello @sepisepsep, The following case was implemented in cPanel & WHM version 76 to ensure the automatic detection feature works when changes are made to the DNS Zone through cPanel: Fixed case CPANEL-20346: Email Routing: Make autodetect setting honor MX entries. Can you verify if your system uses cPanel & WHM version 76 or newer? Thank you.
    0
  • sepisepsep
    Yes, I am using v76.0.20 with CloudLinux 7.6. Kindly note that I made the DNS changes on cPanel and not on WHM.
    0
  • cPanelMichael
    Yes, I am using v76.0.20 with CloudLinux 7.6. Kindly note that I made the DNS changes on cPanel and not on WHM.

    I've been unable to reproduce this behavior on a test environment (I tested using cPanel >> Zone Editor). It's possible the issue relates to how your system is resolving the domain names entered as part of the MX records. Can you open a
    0

Please sign in to leave a comment.