Exchange + Domain name - DNS records

Associate
Joined
29 Apr 2006
Posts
1,456
Hello,
I have my own server (2003) running as a DC+Exchange 2007, and IIS to display web pages.
So far I used both the exchange mail and the IIS for internal purposes only, but now I want others from outside of my lan to be able to either use my exchange services and view the web pages that I host and so on.
I bought a domain name.
Now I am not sure where to start, I took a screenshot of both my DNS server and my domain name dns administration page as they are now.
I understand that I need to add (A) records for the www part and (MX) records for the mail, but I am not 100% on what to fill.


Is there anyone who could give some advice? Is it possible at all to turn the exchange to be "external" now after I have used it internal for quite a long time? without deleting anything etc.
any help appreciated.
 
also as you can see in the picture, when i try to add an mx record - under the mail server i should be typing in the server ip address no? it keep saying "mail server is not valid".
 
It can be anything, but you must first create an A record eg. mail.domain.com pointing to your external IP address, the add that in the mx records page.

BTW if you just want external access you don't have to add anything to your internal DNS
 
YOu need to set up a recipient policy that gives it an external SMTP address. A recipient policy applies email addresses to user account. The bit your showing there is the LOGON domain so it should be your internal domain as shown.
 
Add A record for: mail.yourdomainname.com
Add MX to be mail.yourdomainname.com

Contact your ISP and ask for reverse DNS to point to mail.yourdomainname.com (This is so that your domain name is a FQDN).

As oddjob has said you need to add a receipient policy otherwise you will need to add your external address to every account.
 
thanks guys,
think i got it all sorted now.
1 more thing tho - what if my ISP is a @#$%@# and doesn't allow me to have a static IP, is there any way around this? will be annoying to update the dns records on the domain managment page every time my IP changes. (it doesn't happen much tho, server rarely goes down etc).

Contact your ISP and ask for reverse DNS to point to mail.yourdomainname.com (This is so that your domain name is a FQDN).
Could you please explain what reverse dns does other than resolving IP->name? or what do i need it for really in this case.
Adding a reverse DNS zone on MY dns server won't do?
 
Last edited:
thanks guys,
think i got it all sorted now.
1 more thing tho - what if my ISP is a @#$%@# and doesn't allow me to have a static IP, is there any way around this? will be annoying to update the dns records on the domain managment page every time my IP changes. (it doesn't happen much tho, server rarely goes down etc).
You really really shouldn't be running your primary MX mail server on a dynamic IP address. Not only will you have problems with inbound email if and when the address changes but, assuming your outbound mail is using MX resolution rather than the ISP's smarthost, you'll end up falling foul of blacklisting systems which refuse to accept SMTP connections from dynamic IP addresses.
 
thanks guys,
think i got it all sorted now.
1 more thing tho - what if my ISP is a @#$%@# and doesn't allow me to have a static IP, is there any way around this? will be annoying to update the dns records on the domain managment page every time my IP changes. (it doesn't happen much tho, server rarely goes down etc).


Could you please explain what reverse dns does other than resolving IP->name? or what do i need it for really in this case.
Adding a reverse DNS zone on MY dns server won't do?

If you have a dynamic IP then your ISP will more than likely block port 25.

rDNS is quite useful because some MTA do rDNS checking on the domain and block mail if it isnt set up... for this reason I would set up reverse DNS if your ISP will allow it.

What ISP are you with?
 
Could you please explain what reverse dns does other than resolving IP->name? or what do i need it for really in this case.
Adding a reverse DNS zone on MY dns server won't do?

I'm guessing from your posts that this is for personal/home use and not a "business" setup in which case your ISP will probably not agree to set up a PTR record for you. I would just forward all outgoing traffic through your ISPs smarthost. Adding to your local server means nothing to the outside world. If you have a dynamic IP, set up an account with someone like Dyndns
 
I'm guessing from your posts that this is for personal/home use and not a "business" setup in which case your ISP will probably not agree to set up a PTR record for you. I would just forward all outgoing traffic through your ISPs smarthost. Adding to your local server means nothing to the outside world. If you have a dynamic IP, set up an account with someone like Dyndns

Some residential ISP's will allow this... :)
 
Back
Top Bottom