mkavinsky
asked on
Whose IP to use for MX Record (ISP or Hosting company)
Experts,
Silly question but we currently have an outside firm hosting our mail. We are implementing SBS 2003 and will be having mail hosted ourselves. When we tell our current host to point the MX Record to us (our clients are currently using POP3 to grab their mail from our hosting firm) what IP am I telling them?
I have 2 different numbers? One I got from our DSL provider 67.39.xxx.xxx (I believe this points to our router/firewall and then from there I need to forward port 25 to our internal server - 192.168.1.1) and another is from our current host which is 69.49.xxx.xxx
I assume I am using the first number from our DSL provider?
I am just confused about where to have the MX Record point to now so we can recieve mail.
Thanks
Silly question but we currently have an outside firm hosting our mail. We are implementing SBS 2003 and will be having mail hosted ourselves. When we tell our current host to point the MX Record to us (our clients are currently using POP3 to grab their mail from our hosting firm) what IP am I telling them?
I have 2 different numbers? One I got from our DSL provider 67.39.xxx.xxx (I believe this points to our router/firewall and then from there I need to forward port 25 to our internal server - 192.168.1.1) and another is from our current host which is 69.49.xxx.xxx
I assume I am using the first number from our DSL provider?
I am just confused about where to have the MX Record point to now so we can recieve mail.
Thanks
Your POP clients do not use the MX record. They *can* be using a DNS entry, though, such as "popserver.yourdomain.tld"
The MX record *is* used by remote SMTP senders to find out where to send mail for your domain. So bring up your internal server and configure the port forward, and only when you update the MX record to point to your DSL will inbound email start coming to your new server, and stop going to the hosting company.
Suggestions:
1. You might want to use something like fetchmail (runs on Linux) to collect any leftover email on the hosting server and deliver it to the new server.
2. DNS information tends to get cached all over the Internet, so in fact while email may start coming to the new server almost as soon as the MX record changes, it may not STOP coming to the hosting company for 8-24 hours, or perhaps even more. There are a couple of ways to try and "fix" this, but they don't solve the problem of users who have some messages waiting on one server and some on the other -- so I recommend that you set up fetchmail or an equivalent to solve THAT issue, and the DNS caching becomes unimportant.
The MX record *is* used by remote SMTP senders to find out where to send mail for your domain. So bring up your internal server and configure the port forward, and only when you update the MX record to point to your DSL will inbound email start coming to your new server, and stop going to the hosting company.
Suggestions:
1. You might want to use something like fetchmail (runs on Linux) to collect any leftover email on the hosting server and deliver it to the new server.
2. DNS information tends to get cached all over the Internet, so in fact while email may start coming to the new server almost as soon as the MX record changes, it may not STOP coming to the hosting company for 8-24 hours, or perhaps even more. There are a couple of ways to try and "fix" this, but they don't solve the problem of users who have some messages waiting on one server and some on the other -- so I recommend that you set up fetchmail or an equivalent to solve THAT issue, and the DNS caching becomes unimportant.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
A little mistake from sriwi...
DNS=port 53
SMTP=port 25 (not 110)
POP3=port 110
Leeman
DNS=port 53
SMTP=port 25 (not 110)
POP3=port 110
Leeman
Use the 67.39.xx.xx and forward port 25 traffic to 192.168.1.1