Configuring Local Exchange POP3 / Dns Problems

[Guest joshyme1@gmail.com]

I am using Windows 2003 Enterprise which is overkill but we are

running a specialized application that will not run on Windows Server

small business. I have installed Exchange 2003 and plan to use

iGetmail. My problem lies that I have evidently configured something

wrong with DNS. My server name is topdog and my domain name is the

same to which I will be receiving email. Now when I go to my server

and attempt to use it, it doesnt recognize it as an internet address

and comes back with a reply from its local address 192.168.1.101.

Therefore when I configure the iGetmail program it doesn't recognize

my mail server.

 

This is probably over kill for a small office, but something I want to

do and have some shared mailboxes, etc.

 

Any assistance would be appreciated.

 

Thanks.

[Guest Lanwench [MVP - Exchange]]

Re: Configuring Local Exchange POP3 / Dns Problems

 

joshyme1@gmail.com wrote:

> I am using Windows 2003 Enterprise which is overkill but we are

> running a specialized application that will not run on Windows Server

> small business. I have installed Exchange 2003 and plan to use

> iGetmail.

 

Don't use POP connectors - they're bad news and are not recommended. If you

have a registered Internet domain, just host your mail directly. You can do

this even with a dynamic public IP, although a static is preferred. See

http://www.msexchange.org/tutorials/MF002.html.

> My problem lies that I have evidently configured something

> wrong with DNS. My server name is topdog and my domain name is the

> same to which I will be receiving email.

 

This is called "split brain DNS" and can cause problems, although you can

work around them....it's usually best to avoid it. You can't change it now

but keep this in mind for the future. You should've used something else -

mydomain.local or mydomain.lan or internal.mydomain.com.

> Now when I go to my server

> and attempt to use it, it doesnt recognize it as an internet address

> and comes back with a reply from its local address 192.168.1.101.

> Therefore when I configure the iGetmail program it doesn't recognize

> my mail server.

 

Open your DNS management console on the server - find the forward lookup

zone - add an entry for mail (or whatever you use before .mydomain.com for

the public/external server) and give it the correct public IP. Do the same

for www if you have a public website.

 

However - you should still avoid the necessity of this by not using a POP

connector :-)

>

> This is probably over kill for a small office, but something I want to

> do and have some shared mailboxes, etc.

 

Use Exchange properly and it will be good for your office - try posting

future Exchange questions in microsoft.public.exchange.admin.

>

> Any assistance would be appreciated.

>

> Thanks.