"Jigsore42" <Jigsore42@discussions.microsoft.com> wrote in message
news:274F0A2E-9223-442C-8242-FC5AE4AB3F20@microsoft.com...
>I apologize if this is in the wrong place; it seems to be an IIS/SMTP issue
> more so than Exchange 2000 General.
>
> We have a multi-domain E2K/W2K (IIS 5.0) native mode setup. The domain
> names
> are not "registerable" in internet DNS; our root domain has a domain name
> of
> company.local for example.
>
> Due to recent restrictions that sending SMTP servers have reverse DNS
> lookups, some domains (aol.com, etc.) refuse to accept email from our
> servers. Will the following scenario work?
>
> - add internet DNS records for all E2K servers (both host and pointer
> records)
> - for each exchange sever, go into Exchange System Manager and change the
> FQDN (under the virtual SMTP server properties) to match the entry listed
> in
> internet DNS
>
> Do I need to change anything in IIS, or is making the changes under the
> virtual SMTP server object in ESM sufficient? Aside from the firewall
> implications, will changing the FQDN in ESM cause the connectivity to the
> other E2K servers in other sites to break? In other words, what changes
> (if
> any) do I need to make in order for mail to be sent/received within my
> organization if I make these FQDN changes to ESM? Do I need to add a
> forward
> zone for my internal DNS?
>
> Any input would be greatly appreciated.