Rouge MX Record

Discussion in 'Installation/Configuration' started by z33k3r, Jun 2, 2009.

  1. z33k3r

    z33k3r New Member

    Rouge MX Record - [SOLVED]

    Quick help topic:

    I had a domain full functional and working, but then I realized that the mail server was set to Localhost when it was in actuality a remote server. So I changed it over to remote and saved. Now if I dig from the command line, I still get the localserver as the MX record. I need to clear it so that it looks to the outside world for direction...

    How would one go about doing this?
     
    Last edited: Jun 5, 2009
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    MX records have nothing to do with the remote server setting. To change the mx server you have to change the dns settings for the domain
     
  3. z33k3r

    z33k3r New Member

    Ok, so...

    Ok, I see you and raise you a, "Where/what do I change to maket his work?"
     
  4. falko

    falko Super Moderator ISPConfig Developer

    You have to modify the DNS records on the authoritative nameservers for your domain. You can out these nameservers by running
    Code:
    dig ns yourdomain.com
     
  5. z33k3r

    z33k3r New Member

    So I have checked my sources and from the server, it states that the name servers are in the right place (off site). Using MXtoolbox.com, tested and verified that the MX pointed to a mail.domain.tld and then that resolved IP had a correct reverse DNS entry.

    But... when I "dig type mx domain.tld" i get the sever's IP address... Thus my rouge record...
     
  6. z33k3r

    z33k3r New Member

    Anybody have pointers here? I am not a DNS guy by any means...
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    Please post the exact dig command you used and the completeoutput that you got.
     
  8. z33k3r

    z33k3r New Member

    Sorry to change directions here, but I check DNS and it has updated fully. Now I started looking in the mail logs and I am getting the following in my Postfix logs (edited for privacy):

    Code:
    Jun  4 09:08:56 ts1 postfix/pickup[12452]: 26662C3409F: uid=33 from=<www-data>
    Jun  4 09:08:56 ts1 postfix/cleanup[13168]: 26662C3409F: message-id=<[email protected]>
    Jun  4 09:08:56 ts1 postfix/qmgr[654]: 26662C3409F: from=<[email protected]>, size=1694, nrcpt=1 (queue active)
    Jun  4 09:08:56 ts1 postfix/local[13261]: 26662C3409F: to=<[email protected]>, relay=local, delay=0.06, delays=0.05/0/0/0.01, dsn=5.1.1, status=bounced (unknown user: "user")
    Jun  4 09:08:56 ts1 postfix/cleanup[13168]: 36348C340BC: message-id=<[email protected]>
    Jun  4 09:08:56 ts1 postfix/bounce[13289]: 26662C3409F: sender non-delivery notification: 36348C340BC
    
    As you can see, it's trying to deliver locally instead of on the appropriate remote server...
     
  9. z33k3r

    z33k3r New Member

    Do I need to add a slave record or something in the DNS manager (I don't host the dns, though i have the req. DNS software installed for ISPC)?
     
  10. falko

    falko Super Moderator ISPConfig Developer

    Is targetdomain.tld listed in /etc/postfix/local-host-names?
    What's in /etc/resolv.conf?
     
  11. z33k3r

    z33k3r New Member

    The target domain does appear in the /etc/postfix/local-host-names but only as targetdomain.tld. There isn't a www.targetdomain.tld like the rest of the entries...

    /etc/resolv.conf =
     
  12. z33k3r

    z33k3r New Member

    Removed the entry for targetdomain.tld out of the /etc/postfix/local-host-names file and restarted Postfix... seems to be working now. Thanks Falko :D
     

Share This Page