Re: Can't receive mail from some domains

Hi Lanwench,

My ISP's primary and secondary nameservers as listed in dnsreport.com are
different to those I put in on my sbs box when running the ciecw. They're
also different to the DNS servers picked up automatically by my adsl
modem/router. Will this make a difference? If not what questions should I ask
them?

I know for a fact that two of the domains which are unable to e-mail us send
their mail out through a smarthost who happens to be the same ISP! One of
them gets the 5.1.1 NDR and the other receives nothing back at all. Both
domains are sister companies and really need to connect with us.

Help!

Thanks.

"Lanwench [MVP - Exchange]" wrote:

In news:F877707E-DAEA-412E-84E5-D3F0A1CE06F1@xxxxxxxxxxxxx,
Dave G <DaveG@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Ah Lanwench, I was hoping you'd reply. I have a soft spot for you,
having browsed the forum from afar!

Say, that isn't you in the unmarked van across the street, is it? If it is,
would you mind picking up my shirts at the cleaners while I'm at a client's
office this afternoon?



Strange, when I ran dnsreport.com earlier today (and yesterday) it
reported no errors. The 2 errors it gives now, should they affect
delivery of mail to my server? I thought these were errors with the
ISP name servers? Can I do anything about this?

You should definitely contact the dudes who manage the nameservers & your
public DNS. There's clearly a problem, if you know your firewall is
configured properly and you can telnet on port 25 to your public IP from the
internet ....which I can do easily enough right now.

Post back, and remember I asked for *light* starch on the blue one.


Thanks a lot.

"Lanwench [MVP - Exchange]" wrote:

In news:49DC65DF-373C-4C30-94D1-18D1C92D6E78@xxxxxxxxxxxxx,
Dave G <DaveG@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Hi all, really hope you can help me with this one. Just completed a
standard SBS 2003 R2 installation using our own mail server and DNS
routing. The problem is that users can receive messages from some
domains but not others. Sending is fine. The problem domains either
receive a NDR or, in some cases, nothing at all. The NDR is as
follows: --------------------------------------------------
Reporting-MTA: dns;HESA03UKER.HE.LOCAL
Received-From-MTA: dns;C2bthimr10.btconnect.com
Arrival-Date: Fri, 27 Oct 2006 14:28:08 +0100

Final-Recipient: rfc822;cathyb@xxxxxxxxxxxxxxxx
Action: failed
Status: 5.1.1
----------------------------------------------------

The NDR comes from postmaster@xxxxxxxx - cathyb@xxxxxxxxxxxxxxxx is
a valid address and has been receiving external mail from other
domains.

I have set the A and MX records with my ISP and everything seems to
check out on dnsreport.com. The DNS records at my ISP are:

A mail 81.138.23.69 (my mailserver IP)
CNAME www home.btconnect.com
CNAME ftp home.btconnect.com
CNAME mail mail.btconnect.com
FRAME @ www.newcapital.co.uk
MX @ ibmr.btconnect.com 20
MX @ mail.newcapital.co.uk 10
(my mailserver)

I have had the ISP set up a reverse DNS entry for my mailserver. I
am using the IMF but have removed recipient filtering from AD.

Really not sure what the problem is (nothing in the event viewer
helps) but I had two initial thoughts. Should the secondary MX
record for btconnect.com be removed? Also, we were notified two
days ago that the reverse DNS request had been actioned but told
that it could take up to 5 days to be fully operational. Could this
be the problem?

Hmmm -

http://www.dnsreport.com/tools/dnsreport.ch?domain=newcapital.co.uk
reports some errors.


Any pointers from you good people would really be appreciated. Let
me know if you need any more info.

Many thanks!




.

Relevant Pages

  • Re: Exchange Help!!!!
    ... Best not to have your ISP host your DNS, ... up on the Qwest Servers before actually changing the name servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Bringing DNS In-house
    ... I would handle all of you internal dns resolutions internally and those addresses that you can't resolve forward to your isp. ... It is a good practice to forward all requests to your isp thereby having the ISP do all the lookup work and not expose your internal ip addresses. ... For failover I have 2 seperate internet feeds with 2 seperate ... ISP (as we use their name servers for our domain name). ...
    (microsoft.public.windows.server.dns)
  • Re: Bringing DNS In-house
    ... I would handle all of you internal dns resolutions internally and those addresses that you can't resolve forward to your isp. ... It is a good practice to forward all requests to your isp thereby having the ISP do all the lookup work and not expose your internal ip addresses. ... For failover I have 2 seperate internet feeds with 2 seperate ... ISP (as we use their name servers for our domain name). ...
    (microsoft.public.windows.server.dns)
  • Re: SMTPSVC - Event 2012 and 2013
    ... I got confirmation from my ISP that they had problems with their DNS ... They gave me the IP address of one of their other DNS Servers. ... You're right it doesn't seem to be a permanent fix and I ...
    (microsoft.public.exchange.admin)
  • Re: SMTP, X400... routing no worky
    ... Most likely we are either unable to resolve the MX record from DNS for the domain we are sending too ... ... You can test this by using Nslookup From the Exchange server to verify you can find the MX record for "yahoo.com" then try telneting on port 25 to that IP. ... get a 290 NDR message from the x400 protocol. ... ISP DNS has its MX records to our Natted ...
    (microsoft.public.exchange.admin)