Recipient address rejected on domain after moving to Cloudflare

Discussion in 'ISPConfig 3 Priority Support' started by Stelios, Jun 28, 2024.

  1. Stelios

    Stelios Active Member HowtoForge Supporter

    Hi all,

    I moved the DNS of a domain to Cloudflare and after a day or so I delete the local dns entry from the master and slave DNS.
    I got an email from that domain today and tried to reply back and getting the following error:

    reject: RCPT from controlpanel.mydomain.com[myip]: 450 4.1.2 <[email protected]>: Recipient address rejected: Domain not found; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<webmail.mydomain.com>

    Of course the domain is under email as I haven't changed anything apart from the DNS part.

    Any help is very much appreciated.
     
  2. Stelios

    Stelios Active Member HowtoForge Supporter

    ok this is very strange.
    I cannot lookup the domain at all from within the server:


    Code:
    stelios@controlpanel:~$ nslookup mydomain.com
    ;; Got SERVFAIL reply from 8.8.8.8, trying next server
    Server:        8.8.4.4
    Address:    8.8.4.4#53
    
    ** server can't find mydomain.com: SERVFAIL
    
    Of course if I run a nslookup from any other server it works fine.
    I even changed the DNS under resolv.conf with Google's just to check and same error.

    Any idea what is happening?
     
  3. Stelios

    Stelios Active Member HowtoForge Supporter

    Even if I add 1.1.1.1 which is Cloudflare IP it does not resolve that domain. It is only that domain that has the problem; there are many more in Cloudflare and all are able to resolve.
     
  4. Stelios

    Stelios Active Member HowtoForge Supporter

    Update. The problem somehow relies into ISPConfig for that domain. I got on this multi server setup a few servers on a different location and no matter where the server is none can resolve that domain. All the rest are working fine.
    Any idea how to troubleshoot this?
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig is not involved in resolving domain names at all. According to your output, its Google's name servers that fail to resolve the domain name.
     
  6. Stelios

    Stelios Active Member HowtoForge Supporter

    @till I tried many different DNS and all return the same. It is like ISPConfig is trying to resolve that domain from internal DNS.
    Any other site resolves fine, it is only that domain that doesn't work and from anywhere outside the ISPConfig servers it resolves and work fine.
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig is not involved in resolving names at all. See my post above. It's your Linux system that does this, not ISPConfig. And your Linux system is doing this based on whats configured in the network settings of your server and likely also what's configured in /etc/resolv.conf file.

    You posted this above, this shows that the Google name servers where contacted and that Google replied with SERVFAIL.
     
  8. Stelios

    Stelios Active Member HowtoForge Supporter

    How do you explain that same DNS (google's or whatever) works fine from any PC/server outside ISPConfig?
     
  9. Stelios

    Stelios Active Member HowtoForge Supporter

    ok found the problem, it was with the DNSSEC, I've disabled it and works fine.
     

Share This Page