Timsy321
asked on
Exchange Server 2007 and GoDaddy setup
I could really use some help with setting up an Exchange Server enviornment on my home network using GoDaddy and Exchange Server 2007. I currently have a domain that my lab enviornment is on (lab.net) through Active Directory and the DNS server role. How do I setup my Exchange server and email addresses to point to my GoDaddy name (sky-live.net). I have only run the default setup configurations for my Exchange Server 2007 server and everything is setup. I currently use dydns.org to connect to my home's router IP because I do not currently have a static IP. Is it possible to setup my network so Exchange can send/receive emails over the internet from my (sky-live.net) GoDaddy domain? If so what is the best way to configure my settings to allow for this? I will need to setup the A record and MX records I'm assuming - but other than that I'm at a stand still. Any help would be greatly appreciated, Thanks!
Rick Fee
Save yourself a headache and get a static IP. If you really want to use this for sending and recieving email to the internet get a static. There are a number of issues with dynamic IPs.
ASKER
Alright, That's probably the best advice. Now once I get a static IP what is the best setup?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you are using Static then instead of pointing to your dyndns account, you should set up an 'MX' record that refers to your static IP.
shaun
shaun
Best setup...overview:
Setup reverse DNS
MX Records...ensure your host headers are matching the reverse DNS
You can also setup a SPF
Setup reverse DNS
MX Records...ensure your host headers are matching the reverse DNS
You can also setup a SPF
ASKER
Shauncroucher, thanks for the detailed explanation/instructions. I will try them as soon as possible. Will there be a lot of issues with using dyndns? It sounds like it should be relatively similar to having a static because my Router is automatically updating the dyndns to my current IP.
I have used dyndns a lot for servers I use for testing but if this is going to be a production server then you definitely need a static IP. What if the updater programs fails to update after an IP change using dyndns = mail server unreachable, which is fine in testing but no good for production servers.
Shaun
Shaun
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Whats the best way to find my ISP's SMTP Server address? I have Midcontinent Communications
Look for Outlook Express instructions on their web site. See what they tell them to use for their outbound server.
Simon.
Simon.
ASKER
I cannot create an ARECORD in goDaddy for my '@' to my dyndns account. It says i have to have an IP address (numbers) not a a domain name. My dyn name is sky-net-home.homeip.net - What else are my options to point my ARECORD to an IP if i don't have a static?
You don't need a record for @
All you need is the MX record host name - which can be your dynamic DNS host, and then whatever host name you are using for OWA etc and then autodiscover.example.com, both of which can be CNAMES to the dynamic DNS host name.
Simon.
All you need is the MX record host name - which can be your dynamic DNS host, and then whatever host name you are using for OWA etc and then autodiscover.example.com, both of which can be CNAMES to the dynamic DNS host name.
Simon.
ASKER
Currently i have
ARecords:
@ 12.345.678.912
CNAMES:
www sky-net-home.homeip.net
MX:
@ sky-net-home.homeip.net
What am I doing wrong?
ARecords:
@ 12.345.678.912
CNAMES:
www sky-net-home.homeip.net
MX:
@ sky-net-home.homeip.net
What am I doing wrong?
That would be fine. The top @ record could be set to whatever the default is on GoDaddy. It is basically a wild card in the domain.
The only additional things you need are the record for autodiscover.
www is usually pointed at your public web site. I certainly wouldn't want to point it at an Exchange server.
Simon.
The only additional things you need are the record for autodiscover.
www is usually pointed at your public web site. I certainly wouldn't want to point it at an Exchange server.
Simon.
ASKER
I'm still unable to get mail to send or receive. I have my send connector setup:
Address space Tab: Type: SMTP Address: *
Network Tab: Route Maile Through the following smart hosts: smtp.midco.net (my isp)
Source Server Tab: EXCHANGE-MAIL (my server name)
I'm still a little hazy on how to setup my Accepted Domains - I added sky-live.net as an authoritative domain?
Address space Tab: Type: SMTP Address: *
Network Tab: Route Maile Through the following smart hosts: smtp.midco.net (my isp)
Source Server Tab: EXCHANGE-MAIL (my server name)
I'm still a little hazy on how to setup my Accepted Domains - I added sky-live.net as an authoritative domain?
Does your ISP allow port 25 inbound?
If you have only just make the changes to your DNS records then there is a good chance that the changes haven't gone live yet.
Simon.
If you have only just make the changes to your DNS records then there is a good chance that the changes haven't gone live yet.
Simon.
ASKER
On my router i have port 25 and 443 pointing to my Exchange Server's internal IP (192.168.x.x). My MX Record @ points to my routers dyndns address.
I think i have something not setup right with Send / Receive Connectors. The send is as stated above at my 3:26 pm comment.
I think i have something not setup right with Send / Receive Connectors. The send is as stated above at my 3:26 pm comment.
If your ISP doesn't allow inbound port 25, then it doesn't matter what you have configured on your router or server. It isn't going to work.
Without doing anything to Exchange, you should be able to telnet to port 25 on your IP address and get the SMTP banner. If you cannot then the port isn't open.
If you not using an Edge, then this blog posting will help.
http://msexchangeteam.com/archive/2006/11/17/431555.aspx
Times mean nothing, not all of us are in the USA. It is almost 10pm here.
Simon.
Without doing anything to Exchange, you should be able to telnet to port 25 on your IP address and get the SMTP banner. If you cannot then the port isn't open.
If you not using an Edge, then this blog posting will help.
http://msexchangeteam.com/archive/2006/11/17/431555.aspx
Times mean nothing, not all of us are in the USA. It is almost 10pm here.
Simon.
ASKER
CheckDNS.net results:
CheckDNS.NET tests mail-servers:
Domain sky-live.net has only one mail-server Checking mail server (PRI=0) sky-net-home.homeip.net [208.107.XXX.XXX Error connecting to mail server sky-net-home.homeip.net [208.107.XXX.XXX] port 25 : timed out waiting for connection Some of your MX do not work properly
I telneted to the mail.midco.net and smtp.midco.net [25] and didnt get a response. I have my router setup to forward port 25 to my Exchange server, so then my exchange server isnt contacting my smtp.midco.net isp ?
CheckDNS.NET tests mail-servers:
Domain sky-live.net has only one mail-server Checking mail server (PRI=0) sky-net-home.homeip.net [208.107.XXX.XXX Error connecting to mail server sky-net-home.homeip.net [208.107.XXX.XXX] port 25 : timed out waiting for connection Some of your MX do not work properly
I telneted to the mail.midco.net and smtp.midco.net [25] and didnt get a response. I have my router setup to forward port 25 to my Exchange server, so then my exchange server isnt contacting my smtp.midco.net isp ?
Telnetting to the ISPs SMTP Servers should work. If it does not then something is blocking locally. Router, firewall on Windows, AV, all can do that.
Simon.
Simon.
ASKER
In Server 2008 telnet client via cmd - with firewall disabled - i am using the command
open smtp.midco.net [25]
and getting "could not open connection to the host
open smtp.midco.net [25]
and getting "could not open connection to the host
ASKER
Here is a screenshot of my current setup on GoDaddy
GoDaddy-DNS.jpg
GoDaddy-DNS.jpg