RE: New Exchange 2003 Install
- From: "Donavon Yelton" <dyelton@xxxxxxxxxxxxxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Fri, 9 Apr 2004 13:29:09 -0400
Are you running your own DNS server or a third-party DNS like your ISP?
Our domain is a .local and obviously there is no .local domain on the
net, it's an internal address only. Set up an A record for your mail
server to point to your exchange external IP and give it a name like
mail. Setup a pointer record with the same info as the A record and
then setup your MX record pointing to your a record. You'll need to do
this DNS setup for each domain that you want e-mail going to. As long
as the .com is in your exchange recipient policy it will route it
appropriately once inside your private network.
-----Original Message-----
From: Javier [mailto:jleypon@xxxxxxxxxxxxx]
Sent: Friday, April 09, 2004 1:52 PM
To: [ExchangeList]
Subject: [exchangelist] RE: New Exchange 2003 Install
http://www.MSExchange.org/
Donavon,
Since our company has a domain controller of .net the FQDN in exchange
server get tied to that .net. How do I make the DNS .com point to
exchange if it does not exist? When I try to change the FQDN to .com it
say's domain does not exist.
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security
Resource Site: http://www.windowsecurity.com/ Network Security Library:
http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
Other related posts:
