Setup DNS for a public domain to use with Exchange 2007
I was wondering if anyone has any experience with this. I will deploy Exchange 2007 and host our own email instead of using POP3 with Outlook. I have AD setup with domain.local format. DNS is working properly and our outlook clients have 2 accounts: 1 for local email and for external. I would like to be able to use one account only and that is why I will deploy the new server with EX2007 My problem is how to setup the DNS so that all email sent to domain.com will be routed to my server? Right now in my DNS I have a zone for domain.local zone. I was thinking to create a new zone for my domain.com zone, create a A host with the public IP of the Exchange server, then a MX Record that will point to that Host record. then, finally call our ISP and tell them that we will be from now the "official" DNS server and not the company that currently host our POP3 mailboxes. Is this the right step?
September 17th, 2009 11:21pm

What u said is partially correct, but not...Well to receive mails from external.. You must do changes on your public DNS server... to achieve this... Call your Domain registrar (Domain.com)and askthem to create a MX record with a host name and associate the public IP which is natted to your In-House Exchange server.Once done, cross check the Status through Nslookup from any place..nslookup>Set q=mx>Domain.com>........ It must show your MX record and associated IPNow u'r MX is created and populated globally... and can receive mails...
Free Windows Admin Tool Kit Click here and download it now
September 17th, 2009 11:47pm

Well right now the MX record is hosted by the company that's hosting our website and POP3 emails. Should I work with them on doing this or should I just get a hold of Network Solutions since they are the domain registrar? Can you provide more details on the nslookup part? Is that a test or is the actual creation of the MX record? Thank you for the help
September 21st, 2009 7:26pm

NSLOOKUP is used to test your Public and Local DNS server records..Contact your Domain registra and ask him for the changes to be done on your DNS server...If the Public DNS server of your domain is maintained by your Domain registra he can help you out.. Presently the MX record IP is pointed to the company which is hosting your POP3 mails, change that IP to your Public IP which is nattd to your In-House Exchange.List of NSLOOKUP Commandshttp://support.microsoft.com/default.aspx/kb/200525
Free Windows Admin Tool Kit Click here and download it now
September 22nd, 2009 4:43am

Hi,Additionally, please create the domain.com as Accepted Domain and thecorresponding RecipientPolicyin the Exchange server. After that, the clients can have permission toreceive the email.For the DNS issue, please just contact the ISP to change the A record which should be pointed to your Exchange server. If you have own DNS server which is public, please just do this operation self.ThanksAllen
September 22nd, 2009 9:00am

So, in conclusion: - do I have to create a new zone? Or all I have to do is to create a Host and give it a static, public IP. Then call the ISP and have them create an MX record that will point to that IP? Thank you.
Free Windows Admin Tool Kit Click here and download it now
September 22nd, 2009 10:40pm

Hi,No new zone needs to be created. If your own DNS serveris not published, we need let the ISP to create the Host and MX record.ThanksAllen
September 23rd, 2009 4:51am

I just talked to my ISP and I do have the ability to go into Control Panel and create any DNS changes such as MX and CNAME and point those wherever I need to. That means I DO have to create a public zone, and then point all the DNS changes that I will make on Network Solution's site to my own server. This means that I do need to create a zone right? How concern should I be about security? Thank you for your help everyone.
Free Windows Admin Tool Kit Click here and download it now
September 23rd, 2009 4:11pm

Your Domain is already registered with Network Solutions ( Ex: Dmain.com ), that means Network Solutions people will create a Zone for your Domainon their DNS servers. (No need to create a Zone and firstly u cannot create on the control pannel)They will only Give Controll panel access, where you can create A / MX / SPF /..records on the backend DNS servers of Network Solutions.Firstly..U have a Local Domain In-House (Domain.Local).. In that Local Domain you have Exchange installed.. (Locally you can send and receive mails without any issue)Assuming You also have a Public IP (Ex: 200.1.2.2) which is Natted to your Local In-House Exchange Server.Now Login to your Network Solutions Control panel, go to DNS Mangement and Create a Host(A) record (Ex: MX1.Domain.com)and assocate your Public IP (200.1.2.2) to it.. Once done Create a MX record and associate the new host record (MX1.domain.com)to it with priority 10.Once Done give 12 to 24 Hours for Global replication....Now if you send any mail from Gmail or any domains..... mails will come and hit your Public IP which is natted to your exchange server..Finally its time to check your Internal network how you will associate the Public IP to your exchange server..RegardsHari This posting is provided "AS IS" with no warranties, and confirms no rights.
September 23rd, 2009 6:10pm

Hi Hari, this question it is a very good discussion, I have the same problem for deploy my Exchange infrastructure, last time i' m was blacklisted. i learn you last respond, i just want to know the step first for example, step 1 > creat the public domain for eg. nocal.com step2 > creat a Host a record eg which must be the FQDN public srvmx01.nocal.com , public ip 212.96.23.186 step 3> in the zone nocal.com , creat a mx record wich must be srvmx01.nocal.com Right now, i need to know at this nivel, wich sould i configure in my Internal DNS (nocal.local) ? nothing more ? how i will associate the Public IP to my exchange server ? Thank you in advance
Free Windows Admin Tool Kit Click here and download it now
March 18th, 2011 4:57am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics