Re: Exchange and Reverse DNS - Here's a Challenge
anonymous_at_discussions.microsoft.com
Date: 04/28/04
- Next message: Sameh Ahmed: "Re: Upgrade E2K To E3K"
- Previous message: John Oliver, Jr. \(MVP\): "Re: Priv stm file keeps growing and server processor load is 100%"
- In reply to: John Oliver, Jr. \(MVP\): "Re: Exchange and Reverse DNS - Here's a Challenge"
- Next in thread: John Oliver, Jr. \(MVP\): "Re: Exchange and Reverse DNS - Here's a Challenge"
- Reply: John Oliver, Jr. \(MVP\): "Re: Exchange and Reverse DNS - Here's a Challenge"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 28 Apr 2004 15:17:21 -0700
I was thinking of that - but I was wondering how this
would resolve the Reverse DNS lookup issue? When e-mail
goes out, won't it appear to come from the first interface
of the ISA Server? That's where it appears to come from
now and part of the reason we're having the Reverse DNS
issue
>-----Original Message-----
>My first question is why have two NIC's on your Exchange
Server? I would
>just have one internal NIC on your Exchange Server.
Publish your mail
>server with ISA Server using the Secure Mail Server
wizard. Your Reverse
>DNS PTR record should point to the external IP of the ISA
Server. This is a
>much more secure setup and will solve your Reverse DNS
lookup issues.
>
>--
>John Oliver, Jr.
>MCSE, MCT, CCNA, Exchange MVP
>Microsoft Certified Partner
>
>"Mike" <mikester209@yahoo.com> wrote in message
>news:5a2201c42d59$20d31460$a501280a@phx.gbl...
>> I'm having an interesting problem with my Exchange
Server.
>> I'm using an Exchange 2000 Server with two network
cards -
>> one connected to the internal network and one connected
to
>> the internet. The internal card is configured to use the
>> ISA server's internal address as it's Default Gateway
>> (making it a secure NAT client).
>> About a month ago, we started getting e-mails sent back
>> citing that there was No Reverse DNS entry for the
domain.
>> I did a search on DNS411.com and found that when I do a
>> reverse DNS lookup, it comes back with the proper domain
>> name and IP Address of the external card of the Exchange
>> Server. However, when I use the Exchange Server to go to
>> www.whatismyipaddress.com - it gives me the external IP
>> Address of the ISA Server - NOT the Exchange Server.
This
>> is where my Reverse DNS problem was coming from. I
removed
>> the ISA Server as the default gateway from the internal
>> NIC on the Exchange server and visited the site again -
>> this time it came back with the external IP Address of
the
>> Exchange Server. Problem solved right? - Wrong
>> After a few days, we noticed that mail was getting
backed
>> up in the queue. I tried everything from creating new
SMTP
>> Virtual Servers to trying to force mail out of the
queue.
>> I could not get mail back out to the internet until I
made
>> it a Secure NAT client again (made Exchange's default
>> gateway the internal IP Address of the ISA Server). And
>> now we are back to certain domains sending mail back
>> because of no reverse DNS entry.
>> Sooo - I'm up for any advice on this one. I thought
about
>> just publishing the Exchange Server with ISA, but I know
>> if that will solve the problem since Exchange will
remain
>> a Secure NAT client - and whatismyipaddress.com will
still
>> give me the first external address of the ISA Server.
>> Anyone have any ideas on what's going on and where I
>> should go next? Thanks in advance for the help!
>
>
>.
>
- Next message: Sameh Ahmed: "Re: Upgrade E2K To E3K"
- Previous message: John Oliver, Jr. \(MVP\): "Re: Priv stm file keeps growing and server processor load is 100%"
- In reply to: John Oliver, Jr. \(MVP\): "Re: Exchange and Reverse DNS - Here's a Challenge"
- Next in thread: John Oliver, Jr. \(MVP\): "Re: Exchange and Reverse DNS - Here's a Challenge"
- Reply: John Oliver, Jr. \(MVP\): "Re: Exchange and Reverse DNS - Here's a Challenge"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
