I don't think that's the case. in fact you should have an internal MX record in your internal DNS, so your internal email wouldn't have to be routed out then bak inside. asus77x, I am not sure what command did you use, but here is an exapmle: lets say you have a domain named exhcnagedomain.com in your DNS you have a forward lookup zone called exchangedomain.com, and in this domain you should have your MX record. from the command line: nslookup set type=mx exchangedomain.com the answer should be the exchange server FQDN, and the IP Address. hope that helps On 12/22/05, Carl Houseman <c.houseman@xxxxxxxxx> wrote: > > http://www.MSExchange.org/ <http://www.msexchange.org/> > > In most cases there is no reason to have an MX record in your AD domain's > (internal) DNS. > > You only need an MX record for your external DNS. > > If your internal DNS and external DNS share the same domain name, then > your command line query must select the external DNS server. > > ------------------------------ > *From:* asus77x [mailto:asus77x@xxxxxxxxxxxx] > *Sent:* Thursday, December 22, 2005 11:21 PM > *To:* [ExchangeList] > *Subject:* [exchangelist] mx record > > > > Hi guys, > > > > I've setup win2k ad + dns + ex2k > > But when I query via command line, I can't found mx record. > > Anybody can help ? > > Thanks. > ------------------------------------------------------ > List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist > Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp > ------------------------------------------------------ > Visit TechGenix.com for more information about our other sites: > http://www.techgenix.com > ------------------------------------------------------ > You are currently subscribed to this MSExchange.org Discussion List as: > mjtech@xxxxxxxxx > To unsubscribe visit > http://www.webelists.com/cgi/lyris.pl?enter=exchangelist > Report abuse to info@xxxxxxxxxxxxxx > -- MJ Almassud A+, N+ CCNA MCSA MCSE+M Cell # 678-768-4854