Re: 550 5.7.1 NDR caused by Exchange using A record instead of MX

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Thanks for the RFC reference David. If you think about it, falling back to
the A RR seems like a very bad idea. My case for example, the MX record is
not returned in the query because of timeout or whatever reason and then the
A record is queried. Can anybody think of a domain that has a website
without the www in front? There are quite a few. If that initial mx query
fails and the A record is queried, we are trying to send mail to the
webserver. Mail servers are so touchy anymore because of SPAM that servers
not using MX records probably fail to work with many servers. So in my
opinion, they should take that requirement out of the RFC?

Stephen

"David Strome" wrote:

> Exchange is required to query the A record if no MX records exist. See RFC
> 2821 section 5 for more information.
>
>
> "Slacker" <Slacker@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:6D1692B2-9240-4943-A01B-7784765B0AF9@xxxxxxxxxxxxxxxx
> >I recently had a user report a 550 5.7.1 NDR to me. After researching the
> > error, I noticed that the message came from an SMTP server that was NOT
> > the
> > proper SMTP server for the domain domain.com. It was an an SMTP server
> > that
> > was running on the webserver for domain.com. The reason that it was
> > connecting to the webserver is that when it did a query for the A record
> > for
> > domain.com it got the IP address of the web server.
> > Both www.domain.com and domain.com have the same IP address.
> > Exchange should have queried the MX record for domain.com and not the A
> > record.
> > I browsed my DNS server logs which had debugging enabled and noticed where
> > the request was made.
> > I would like to know, why did Exchange query the A record??
> > I actually thought that is what it is supposed to do if it can't find an
> > MX
> > record but after thinking about it, that seems like a really bad thing to
> > do.
> > Unless a domain has an A record the same as the MX record, mail delivery
> > will
> > fail.
> > Is there anything I can do to prevent this problem like increasing the
> > timeouts for my forwarders or not allowing Exchange to fall back to A
> > records?
> > Any ideas would be greatly appreciated.
> >
> > Thanks,
> > Stephen
>
>
>
.



Relevant Pages

  • Re: How to combine existing collections to include or exclude...
    ... "Matthew Hudson" wrote: ... Servers you want minus the ones you don't want ... [edit query statement/Criteria] ... Add computers you don't want to show up in Collection B ...
    (microsoft.public.sms.admin)
  • RE: How to combine existing collections to include or exclude...
    ... "Matthew Hudson" wrote: ... Servers you want minus the ones you don't want ... Add computers you don't want to show up in Collection B ... will see if I can't just send you the collection queries and the query ...
    (microsoft.public.sms.admin)
  • Re: router causing strange DNS behaviour?
    ... These cobbled together ISP networks can ... Initial query took about 4.5 secs ... Rogers is a Canadian ISP, and their name servers should have ...
    (comp.os.linux.networking)
  • Re: Troubleshooting slow DNS lookup
    ... RFC 2671 Extension Mechanisms for DNS ... I also done some dnssec trace demonstration, and it still not a good ... RFC 4294 IPv6 Node Requirements ... Well if you ask the root servers .... ...
    (comp.protocols.dns.bind)
  • Re: Boolean query algorithms
    ... Does that mean the query is broken up into 2 processes that are ... also my question relates to how said queries be them sql ... Google use 'chunck servers'. ... any of the 10 chunck servers that hold each chunk of data. ...
    (alt.internet.search-engines)