 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Design / November 2006MX record and smtp
Hi professionals, i would like to setup exchange mail in my company. I understand i need to registered a mx record for mail server and a smtp(port 25) server. Lets say i wanted a FE-BE exchange, where FE handles OWA and Smtp(incoming/outgog mail) Do i need 2 different public IP addresses to registerd a mx record and my smtp?? Is mx record same as smtp? Do they use same IP or can have 2 different IP? A mx record is to inform the public world that ithis is my mail server. A smtp is for public mail transportation. Am i rite of the above? Or can u explain whats needs to be donne... Many Thanks!! > Hi professionals, > [quoted text clipped - 10 lines] > Am i rite of the above? Or can u explain whats needs to be donne... > Many Thanks!! When server in another location wants to send a message to you using SMTP, it looks for your MX record to find out which server handles your mail. Actually, you are not supposed to put an IP address in an MX record, although it will probably still work if you do, since lots of people do that. You are supposed to put a host name (e.g. mail.yourdomain.com) in the MX record, and then create an A (Host) record in the domain (e.g. yourdomain.com) that points the host named 'mail' to the required IP address. You only need one public IP address to achieve this. SMTP is an email protocol (i.e. it defines the way in which two servers exchange information). An MX record is one of your DNS records. Lee.  Signature_______________________________________ Outlook Web Access For PDA , OWA For WAP www.owapda.com email a@t leederbyshire d.0.t c.0.m _______________________________________ ok.. i understand now. Another question is on my firewall portion. If say i do not use ISA server. In my firewall smtp rule, Do i allow smtp port 25 and NAT using this MX record public IP to my internal exchange server? thanks!! > > Hi professionals, > > [quoted text clipped - 32 lines] > > Lee. > ok.. i understand now. Another question is on my firewall portion. If say i > do not use ISA server. In my firewall smtp rule, Do i allow smtp port 25 and > NAT using this MX record public IP to my internal exchange server? > > thanks!! Yes. If you use NAT, then your router has the Public IP address, and you forward incoming port 25 traffic to the server's Private IP address. Lee. Signature_______________________________________ Outlook Web Access For PDA , OWA For WAP www.owapda.com email a@t leederbyshire d.0.t c.0.m _______________________________________ If i were have to use different IP on my ISA WAN interface and the MX record. Is there any other workaround like create another mx record using the isa wan IP? i dun know.. i juz hope i can use different IP....for WAN interface and exchange MX record.... > > ok.. i understand now. Another question is on my firewall portion. > If say i [quoted text clipped - 9 lines] > > Lee. > If i were have to use different IP on my ISA WAN interface and the MX record. > Is there any other workaround like create another mx record using the isa wan > IP? i dun know.. i juz hope i can use different IP....for WAN interface and > exchange MX record.... If your ISP has given you several public IP addresses, then you can probably do this. You just need to correctly route the traffic into your LAN somehow. But if everything comes into your LAN through the ISA server (including SMTP email), then all your DNS records have to point to the ISA server's WAN interface. You can have several MX records, but in general only one will ever be used. The point of having a second or third MX record is to provide an alternative server to handle the mail, if the main one should be down. Lee. Signature_______________________________________ Outlook Web Access For PDA , OWA For WAP www.owapda.com email a@t leederbyshire d.0.t c.0.m _______________________________________ ok.. let says i use the Primary mx Ip on my isa wan interface too. But in event that my primary mx is down... secondary mx kick in... when mails sent out, that mail will still be send out as my isa wan IP, which oso different IP as my secondary mx IP... isn't that i go back to the same problem? > > If i were have to use different IP on my ISA WAN interface and the > MX record. [quoted text clipped - 16 lines] > > Lee. > ok.. let says i use the Primary mx Ip on my isa wan interface too. But in > event that my primary mx is down... secondary mx kick in... when mails sent > out, that mail will still be send out as my isa wan IP, which oso different > IP as my secondary mx IP... isn't that i go back to the same problem? Your MX records aren't used when you send mail out, they are only there for external servers to find your mail server when they want to send something to you. The receiver will check the reverse dns with the Ip, rite? thats wat happen to my current problem. Using different IP on WAn interface and primary MX record...The mail send out used ISA wan IP, when other mail server check for reverse dns.. it checks that my source ip and domain do not tally with my MX record....the mail will recongnise as spoof mail....dats y my domain got black list ...am i i rite?? > > ok.. let says i use the Primary mx Ip on my isa wan interface too. > But in [quoted text clipped - 8 lines] > there for external servers to find your mail server when they want to > send something to you. > The receiver will check the reverse dns with the Ip, rite? thats wat happen > to my current problem. Using different IP on WAn interface and primary MX > record...The mail send out used ISA wan IP, when other mail server check for > reverse dns.. it checks that my source ip and domain do not tally with my MX > record....the mail will recongnise as spoof mail....dats y my domain got > black list ...am i i rite?? I don't think RDNS checks actually looks at the MX records. I think it just checks that the server name supplied when it sends the HELO command matches the public IP address that the mail is coming from. Try a test on your domain using the DNS Report test on the left here: http://www.dnsreport.com . See if anything is flagged as a possible issue. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.