Internal mycompany.com domain and external mycompany.com email host domain are the same, pop3 email problems.
Unfortunately my internal mycompany.com domain address is the same as my external mycompany.com email host (bravenet).
So when clients on the network send a request to pop3.mycompany.com instead of forwarding to the external host it looks for a pop3 server on the internal network. Which will not exist until I install a exchange server in a few months.
In the meantime I can either A make a new mycompany.net email host domain, or B rename the local domain to a .loc.
Does anyone have any other more seamless/easier to implement suggestions?
So when clients on the network send a request to pop3.mycompany.com instead of forwarding to the external host it looks for a pop3 server on the internal network. Which will not exist until I install a exchange server in a few months.
In the meantime I can either A make a new mycompany.net email host domain, or B rename the local domain to a .loc.
Does anyone have any other more seamless/easier to implement suggestions?
ASKER
I thought about this, could you provide a step-step walk-through for creating this DNS forwarder?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Perhaps i should have put beginner on the subject when I made the question:
A step by step would be much appreciated.
A step by step would be much appreciated.
Read this KB:
http://support.microsoft.com/?scid=kb;en-us;323445&x=10&y=7
Section "How to Create a Host Record"
http://support.microsoft.com/?scid=kb;en-us;323445&x=10&y=7
Section "How to Create a Host Record"
ASKER
I get an error relation to the PTR pointer, says "probably" due to the reverse look up zone.
I've gone around to the 20 or so clients and changed their incoming and outgoing mail servers to the IP of the pop3andsmtp, and that seems to have done the temporary fix.
I've gone around to the 20 or so clients and changed their incoming and outgoing mail servers to the IP of the pop3andsmtp, and that seems to have done the temporary fix.
The procedure which has been detailed above by Mitch1981 should have solved this problem. When you have an Exchange Server, POP3 will not be used at all by Outlook clients, so that shouldn't cause you too many problems.
As for the reverse lookup zone error, you can safely ignore that. You received that message because you had the "Create associated PTR record" (a reverse lookup record). Your server attempted to locate the reverse lookup zone for the EXTERNAL POP3 server's IP, obviously it failed, and thus could not create the PTR record. In this case it is safe to ignore that message.
-tigermatt
ASKER
humm well changing the clients incoming and outgoing worked for about 2 days then all of sudden they got 3 duplicates of all the messages on the external webserver..... would directing them straight to the IP have anything to do with this.....?
I wouldn't think so less I'm missing something.
I wouldn't think so less I'm missing something.
If the DNS System is responding with the correct IP address of the remote POP3 server, then that is as far as DNS goes. DNS will not cause duplicate messages to be downloaded and delivered, so the problem could be with some anti-virus software, the remote mail server or some other issue.
The most common cause for duplicates is anti-virus software wrongly scanning your mail databases. Contact the person who manages the POP3 server and inform them of the issue.
-tigermatt
This record will be have the IP address the external pop3 server.
Bye.