[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 228
  • Last Modified:

Local Exchange with GoDaddy

I have a Local Exchange Server 2010 (remote.benchmarkerie.com), which has an A and MX record pointing to it at my GoDaddy domain, benchmarkerie.com.  We are getting sporadic send errors (bounce backs) to various domains.  It doesn't happen all the time and there seems to be no rhyme or reason.  I have a Cisco UC320 at the edge with ports 25 and 587 opened to the local server (192.x.x.x address).  Any thoughts?  Thanks in advance.
0
JRiley562
Asked:
JRiley562
  • 4
1 Solution
 
bigbigpigCommented:
You'll have to look at the SMTP code on the bounce message.  Do you get the messages returned from your Exchange server or from the recipients domain?  Post the SMTP codes from the messages here.
0
 
James HIT DirectorCommented:
Do you have a PTR for your IP address?
Can you post the bounceback error in full?

Go to here:
www.mxtoolbox.com

Type your domain in and run the various tests (MX, PTR, blacklist, etc...)  and post any relevant results.
0
 
JRiley562Author Commented:
Generating server: BENCHMARKSERVER.benchmarkcomp.local
 
name@xyz.com
wh03.suite224.com #553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) ##
 
Original message headers:
 
Received: from BENCHMARKSERVER.benchmarkcomp.local
([fe80::1b34:c04d:ff74:e860]) by BENCHMARKSERVER.benchmarkcomp.local
([fe80::1b34:c04d:ff74:e860%10]) with mapi id 14.02.0342.003; Fri, 24 May
2013 08:30:33 -0400
From: Bob Klemm <Bob@benchmarkerie.com>
To: "name@xyzmix.com" <name@xyz.com>
CC: Service <service@benchmarkerie.com>
Subject: RE: Fwd: Undeliverable: Re: PO 709222
Thread-Topic: Fwd: Undeliverable: Re: PO 709222
Thread-Index: AQDmFijFUUl5AeIzRs6C3DkID/HDRQLLYj0RAo+SWAcB/ptLPAGkWdZTmpzZDuA=
Date: Fri, 24 May 2013 12:30:31 +0000
Message-ID: <9501432114848D4180184D81E89092850A6F0826@BENCHMARKSERVER.benchmarkcomp.local>
References: <OF55690340.D869C9F6-ON85257B74.006E2101-85257B74.006E31C2@xyz.com>
<B0BD73D4-DBAF-4BA2-8FF7-A9A481499461@benchmarkerie.com>,<b2fcda23-c895-4243-a0c3-7c2fd465e3b9@BENCHMARKSERVER.benchmarkcomp.local>
<D1768B4F-CF05-468C-BB78-8E1DCE454C1F@benchmarkerie.com>
<OF0A22909B.AD7B61CB-ON85257B75.0041B29D-85257B75.0041FCF2@xyz.com>
In-Reply-To: <OF0A22909B.AD7B61CB-ON85257B75.0041B29D-85257B75.0041FCF2@xyz.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.0.68]
Content-Type: multipart/related;
       boundary="_005_9501432114848D4180184D81E89092850A6F0826BENCHMARKSERVER_";
       type="multipart/alternative"
MIME-Version: 1.0
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
JRiley562Author Commented:
I have checked mxtoolbox & dnsstuff.  My PTR and MX records appear fine.  I've successfully performed the Microsoft remote Connectivity Analyzer with the following results:

===============================================
      Performing Outbound SMTP Test
       The outbound SMTP test was successful.
       
      Test Steps
       
      Attempting reverse DNS lookup for IP address 74.219.112.90.
       ExRCA successfully resolved IP address 74.219.112.90 via reverse DNS lookup.
       
      Additional Details
      Performing Real-Time Black Hole List (RBL) Test
       Your IP address wasn't found on any of the block lists selected.
       
      Test Steps
      Performing Sender ID validation.
       Sender ID validation was performed successfully.
       
      Test Steps
       
      Attempting to find the SPF record using a DNS TEXT record query.
       The SPF record was found.
       
      Additional Details
      Parsing the SPF record and evaluating mechanisms and modifiers.
       The SPF record was parsed and evaluated successfully.
       
      Test Steps
       
      Evaluating A Record lookup mechanism: "+a"
       
      Additional Details
       The DNS A Record lookup for IP address 74.219.112.90 found no match for domain benchmarkerie.com.
      Evaluating MX mechanism: "+mx"
       The MX mechanism indicated a positive status.
       
      Additional Details

=========================================================
This last test, DNS A Record lookup for 74.219.112.90, is my only remaining question.  This is my ISP-provided internet-facing address and registered on GoDaddy DNS as "remote.benchmarkerie.com", pointing to my Exchange Server.  DO I need to worry about this?
0
 
JRiley562Author Commented:
Fixed.  dnscmd /ClearCache, then doublechecking that 'Use External DNS' was checked on send connector was the answer
0
 
JRiley562Author Commented:
Came across solution through trial & error.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now