Re: Email not getting to Comcast addresses (Reverse DNS failure)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I am running SBS 2003 with a ISP hosted POP3 Mail Server. Incoming mail is
delivered to my ISP’s Server and retrieved my Exchange 2003 server by a POP3
connector. Outgoing email does not go through the ISP’s mail server. Most
email is sent with out a problem. When I send to COMCAST.NET I receive a NDR
stating:

There was a SMTP communication problem with the recipient's email server.
Please contact your system administrator.
<externaldomainname.com #5.5.0 smtp;521-EHLO/HELO from sender
xxx.xxx.xxx.xxx does not map to externaldomainname.com in DNS>

The ip address is the external email address of my SBS 2003 (from NAT). I
have used different internal and external domain name per Microsoft’s
recommendations. For example:
ExternalDomainName.com
LocalDomainName.local

I contacted my ISP and they told me that there is nothing they can do. I
found a place on the ISP’s site where I could add a MX record and/or a CName
record. I believe what I need to do is add a CName to my ISP’s DNS settings
that maps ExternalDomaminName.com name to my LocalDomainName.local external
ip address.

Is it safe to add one or both of these records to my ISP’s DNS setting so
that Comcast.net can resolve the external ip address of my local domain?
This would be the same address that is used for Remote Web Workplace. OWA,
etc…

--
Keivn


""Jenny wu [MSFT]"" wrote:

Hi Shawn,

Thanks for post back. I am glad to know that things are getting fine now. I
appreciate your time and effort to the issue and get this resolved.

Please don't hesitate to post question in the SBS newsgroup in the future.
We are glad to help-).

Have a nice day!

Sincerely,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
The customer mail content:
======================
Jenny,

Thanks for following up. I was able to get Qwest to add a PTR record and
that seems to have solved the problem. I posted this in the newsgroup as
well.

Thanks,
======================

--------------------
X-Tomcat-ID: 278992677
References: <1142540175.974027.165220@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
<1143082369.934696.200310@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
Organization: Microsoft
Date: Thu, 23 Mar 2006 10:35:58 GMT
Subject: Re: Email not getting to Comcast addresses (Reverse DNS failure)
X-Tomcat-NG: microsoft.public.windows.server.sbs
Message-ID: <lF64XWmTGHA.6492@xxxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
Lines: 119
Path: TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.windows.server.sbs:255204
NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182

Hi Shawn,

Thanks for your detail information.

After reviewed your information, I found that the PTR record is configured
incorrectly. I suggest that you contact your ISP (Qwest) to verify it.
The
PTR record should not point to 63.224.51.25. What is the device IP address
is 63.224.51.30?

For every SMTP server or Exchange Server computer that sends outgoing
Internet e-mail, make sure that there is a valid PTR record for the Public
IP address of that sending SMTP server or Exchange Server computer. This
may be a firewall, a router, or another device that used to publish your
domain information to an IP address that is visible by Internet hosts.

For example, your SBS Server is behind a firewall with an internal IP of
10.10.10.1, and the firewall has an external IP of 4.3.2.1. You need
configure a PTR for 4.3.2.1 pointing to a valid host record.

After verified them and then test the issue and let me knew the result. I
am happy to be of assistance to you.

Have a nice day!

Sincerely,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
From: "Shawn" <sjensen@xxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
Subject: Re: Email not getting to Comcast addresses (Reverse DNS failure)
Date: 22 Mar 2006 18:52:49 -0800
Organization: http://groups.google.com
Lines: 27
Message-ID: <1143082369.934696.200310@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <1142540175.974027.165220@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
<0DGyh7YSGHA.7144@xxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 63.224.51.30
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1143082376 16502 127.0.0.1 (23 Mar 2006
02:52:56 GMT)
X-Complaints-To: groups-abuse@xxxxxxxxxx
NNTP-Posting-Date: Thu, 23 Mar 2006 02:52:56 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT
5.0),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@xxxxxxxxxx
Injection-Info: g10g2000cwb.googlegroups.com; posting-host=63.224.51.30;
posting-account=Bjco0Q0AAADkT0gH_Pq3UAhaQoIrWdb8
Path:
TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onl
i
ne.de!border2.nntp.dca.giganews.com!nntp.giganews.com!transit3.readnews.com
!
news-out.readnews.com!postnews.google.com!g10g2000cwb.googlegroups.com!not-
f
or-mail
Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.windows.server.sbs:255133
X-Tomcat-NG: microsoft.public.windows.server.sbs

Jenny,

My apologies for not getting back to you sooner. I had some other
crisis crop up (funny how that always happens).

I've sent a zip file to your email address with the following files
that should have the information that you requested:

ipconfig-report.txt
dcdiag-032206.txt
ex060322.log (SMTP log)
ex060323.log (SMTP log)
dnsreport - Email Tester Results for bdassociates.pdf
dnsreport - DNS Report Results for bdassociates.pdf
Undeliverable Comcast email connection test.msg

I haven't yet contacted Qwest regarding our MX and PTR records because
I'm not sure that the problem isn't actually located on my server.
Hopefully you'll find something useful in the file I sent.

Please let me know what you discover or if you need additional
information.

Thanks for looking into this,

~Shawn






.

Relevant Pages

  • Re: R2 w/ISA User type account cannot use my companys internal website
    ... Alerts\Core Server Alerts ... Microsoft CSS Online Newsgroup Support ... And our product group is still reviewing the impact of the upgrade SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: R2 w/ISA User type account cannot use my companys internal website
    ... can refer to the steps below to reinstall the SBS Monitoring component. ... Select Windows Small Business Server 2003 and then click Change/Remove. ... select Microsoft SQL Server Desktop Engine ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Premium, Sharepoint, CRM
    ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... | In regards to Sharepoint Portal server, it looks like it would be best to ...
    (microsoft.public.windows.server.sbs)
  • Re: publishing multiple websites in ISA 2004
    ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... |> hosted off of a second server that is a member server in the network. ...
    (microsoft.public.windows.server.sbs)
  • RE: path to client not found
    ... configuration with 1 NIC but with the default gateway to the router ... Ethernet adapter Server Local Area Connection: ... > to SBS IP address on all local clients and leave default gateway on SBS ... > and server side to newsgroup, also make sure that you have run CEICW ...
    (microsoft.public.windows.server.sbs)