locked
NAT Issue with reverse lookup ? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    We have just setup an exchange 2010 server up on one of our extra ip addresses, on the firewall (Dlink DFL-800) I have OWA and SMTP traffic nat'd to the internal address of the exchange server.

    Router/Firewall: 2**.***.***.66
    Exchange: 2**.***.***.69

    All works well but some emails are rejected by recipient because the reverse entry is seeing our router ip instead of the exchange ip

    eg.     from mail.seetru.com ([2**.***.***.66])

    when it should be 2**.***.***.69


    any idea what I have to do to resolve this?

    yes, I could use a smart host, but would rather fix this first :D

    Thanks for any advice..
    • Changed type Mike Crowley Thursday, March 17, 2011 12:26 PM
    Tuesday, February 15, 2011 7:47 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    contact your ISP (or do it yourself if you have access):

    setup reverse lookup record in DNS for 2*.*.69 to resolve to your server name

     

    With kind regards
    Krystian Zieja
    http://www.projectnenvision.com
    Follow me on twitter
    My Blog
    Tuesday, February 15, 2011 8:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This is done already and has been for many weeks
    Tuesday, February 15, 2011 8:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    On Tue, 15 Feb 2011 19:47:28 +0000, AntonyBurden wrote:
     
    >We have just setup an exchange 2010 server up on one of our extra ip addresses, on the firewall (Dlink DFL-800) I have OWA and SMTP traffic nat'd to the internal address of the exchange server. Router/Firewall: 2**.***.***.66 Exchange: 2**.***.***.69 All works well but some emails are rejected by recipient because the reverse entry is seeing our router ip instead of the exchange ip eg. from mail.seetru.com ([2**.***.***.66]) when it should be 2**.***.***.69 any idea what I have to do to resolve this?
     
    Correct the external DNS so the FQDN your server sends in its
    HELO\EHLO can be resolved to the 2**.***.***.66 address, and then
    adjust the PTR for the IP address 2**.***.***.66 so it returns the
    name FQDN your server sends in its HELO\EHLO.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     
    --- Rich Matheisen MCSE+I, Exchange MVP
    Tuesday, February 15, 2011 8:32 PM