asked on

Domain name in ADS is not .local - instead it matches the Internet DNS - causing random problems/bounces?

If you have an Exchange Server, that's used as a internal LAN server + Exchange on the Internet, it's usually configured with a .local ADS set up.. but what if a server is configured for ADS and it matches the Internet FQDN and there is no .local - only "server.domain.com" in ADS and Exchange?

There seems to be strange, random bounce issues... 95% of mail flows fine, but sometimes if an outside person "Replies" to a message sent by an internal user, it bounces with '504 Need to Authenticate First".. I suspect it has something to do with the DNS set up and Active Directory..? Any insight into this kind of set up?

ASKER CERTIFIED SOLUTION

Exchange_Geek

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

aconway

ASKER

I said it correctly.. and I tested it twice earlier.. someone from the outside was having a problem sending mail to an inside user.. (see NDR below).. They then discovered if they compose a NEW message to that same user, it goes fine.. but if it's a reply, it bounced.. we tested and confirmed this two times in a row.. So don't ask me.. that's why I am asking you guys.

THEN. shortly after we started testing this, it began to work when replying and is no longer bouncing back.. so it seems like a sporadic problems.. hence my 95% comment... if I have them test it again, it could stat bouncing again.. very random - something is going on.

Here's the NDR from the outside user when they tried to reply and it failed:

There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
<dev1.internal.networkforgood.org #5.5.0 smtp;553 sorry, that domain isn't in my list of allowed rcpthosts (#5.5.3 - chkuser)>

SMTP LOGFILE:

64.236.108.219, OutboundConnectionResponse, 10/20/2008, 10:55:39, SMTPSVC1, SERVER, -, 141, 0, 132, 0, 0, -, -, 220 dev1.internal.networkforgood.org Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Mon, 20 Oct 2008 13:52:21 -0400 ,
64.236.108.219, OutboundConnectionCommand, 10/20/2008, 10:55:39, SMTPSVC1, SERVER, -, 141, 0, 4, 0, 0, EHLO, -, server.mydomain.org,
64.236.108.219, OutboundConnectionResponse, 10/20/2008, 10:55:39, SMTPSVC1, SERVER, -, 281, 0, 57, 0, 0, -, -, 250-dev1.internal.networkforgood.org Hello [69.30.69.184],
64.236.108.219, OutboundConnectionCommand, 10/20/2008, 10:55:39, SMTPSVC1, SERVER, -, 281, 0, 4, 0, 0, MAIL, -, FROM:<user@mydomain.org> SIZE=28208,
64.236.108.219, OutboundConnectionResponse, 10/20/2008, 10:55:39, SMTPSVC1, SERVER, -, 406, 0, 34, 0, 0, -, -, 250 2.1.0 user@mydomain.org....Sender OK,
64.236.108.219, OutboundConnectionCommand, 10/20/2008, 10:55:39, SMTPSVC1, SERVER, -, 406, 0, 4, 0, 0, RCPT, -, TO:<user@networkforgood.org>,
64.236.108.219, OutboundConnectionResponse, 10/20/2008, 10:55:39, SMTPSVC1, SERVER, -, 516, 0, 39, 0, 0, -, -, 250 2.1.5 user@networkforgood.org ,
64.236.108.219, OutboundConnectionCommand, 10/20/2008, 10:55:39, SMTPSVC1, SERVER, -, 516, 0, 7, 0, 0, XEXCH50, -, 2460 2,
64.236.108.219, OutboundConnectionResponse, 10/20/2008, 10:55:39, SMTPSVC1, SERVER, -, 641, 0, 30, 0, 0, -, -, 504 Need to authenticate first,
64.236.108.219, OutboundConnectionCommand, 10/20/2008, 10:55:39, SMTPSVC1, SERVER, -, 641, 0, 4, 0, 0, BDAT, -, 28208 LAST,
64.236.108.219, OutboundConnectionResponse, 10/20/2008, 10:55:40, SMTPSVC1, SERVER, -, 1281, 0, 92, 0, 0, -, -, 250 2.6.0 <4CD38C3641F4D543934F26D2DE489BE39D134C@server.mydomain.org> Queued mail for delivery,
64.236.108.219, OutboundConnectionCommand, 10/20/2008, 10:55:40, SMTPSVC1, SERVER, -, 1281, 0, 4, 0, 0, QUIT, -, -,
64.236.108.219, OutboundConnectionResponse, 10/20/2008, 10:55:40, SMTPSVC1, SERVER, -, 1516, 0, 79, 0, 0, -, -, 221 2.0.0 dev1.internal.networkforgood.org Service closing transmission channel,

... and it magically starts working again.. just trying to figure out the "magic" here.. There is no AV or Mail Security involved, at least on the end I am troubleshooting.. just normal Exchange SMTP DNS..

Or maybe it IS actually sending it through eventually (looking at that log entry).. but it's STILL producing random NDR's, which .. means something is weird.