Announcement

Collapse
No announcement yet.

2003 AD domain is one name public domain is different

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • 2003 AD domain is one name public domain is different

    I am having problems (I think with DNS) on my Exchange server. I have Windows 2003 standard edition server (sp1) and Exchange 2003 (sp1). My inside domain name is computersource.us and my public domain is computersource.ws. I have my mx record with my ISP pointing to my public ip (205.244.100.126). I have my router send all port 25 to my exchange servers ip (cs01m01 192.168.1.50). I can send emails to the outside but cannot receive. When I run dnsreports.com I get 2 errors:

    Connect to mail servers ERROR: I could not find any mailservers for computersource.ws.


    MX Category ERROR: I couldn't find any MX records for computersource.ws. If you want to receive E-mail on this domain, you should have MX record(s). Without any MX records, mailservers should attempt to deliver mail to the A record for computersource.ws. I can't continue in a case like this, so I'm assuming you don't receive mail on this domain.


    Where do I point my mx record on my domain controller? Zone is computersource.us.

  • #2
    Your Internal Domain controller doesn't need to find the MX record for your own domain.

    The problem is with your ISP, providing you didn't hide your real domain name in your post, computersource.ws doesn't have any MX records setup so external mails doesn't know where to route to.

    Topper
    * Shamelessly mentioning "Don't forget to add reputation!"

    Comment

    Working...
    X