Public MX record differs from server name
BLMuzzy
recently:
There was a SMTP communication problem with the recipient's email
server. Please contact your system administrator.
<netbiosname.subdomain.domain.com #5.5.0 smtp;521-EHLO/HELO from
sender 12.34.56.78 does not map to netbiosname.subdomain.domain.com in DNS>
In ESM->...Protocols->SMTP->Default SMTP virtual server
properties->Delivery->Advanced the Fully-qualified domain name was the
NetBIOS name of the server vs the public DNS name. I changed it to the
public DNS name mail.domain.com. I clicked "Check DNS" and it returned "the
domain name is valid".
Do i also need to additionally "Configure external DNS servers" (mine are at
godaddy.com)? According to the help file, "many administrators use this
feature to support internal DNS servers within their intranet, and use
external DNS servers for Internet e-mail." Because Check DNS succeeded, is
this necessary?
thanks,
Bob
Frankster
Frankster
Yes, you need to use the external DNS servers to do this. The outside world
cannot reach your internal DNS servers directly (hopefully!). The fact that
it succeeds inside your network doesn't mean much to the outside world.
-Frank
BLMuzzy
about netbiosname.subdomain.domain.com. After I wrote this last night, I
sent mail to the previously failed recipient and it worked, because the
recipient's SMTP server (at comcast.net) could now match up the advertised
sending SMTP box's FQDN with the public IP of it. That makes sense. I
wasn't sure if there was some other reason for specifying external DNS
servers; like if that would somehow confuse internal email delivery or
something. But all appears OK for now.
thanks!
"Frankster" <Fr...@SPAM2TRASH.com> wrote in message
news:jOCdndSn7dvB6MHY...@giganews.com...