Announcement

Collapse
No announcement yet.

PTR needs FQDN - .com vs .local

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • PTR needs FQDN - .com vs .local

    We may need to work through some of this, but here is where I am:'

    I've read info on this, but want to make sure that I'm clear on this.

    - Our internal domain ends in a .local
    - Our Exchange 2007 internal receive connector is set to the .local (which is fine), and our external send connector is ACTUALLY blank (this should be a .com to answer EHLO for the PTR lookup by receiving servers, being blank means there is no preconfigured answer - correct?). I understand that the internal and external can be different.

    BTW, most email is working except a few that have a

    Being that the .local is not valid and the .com is, then our external connector and our PTR record should be a mail.companyname.com to the DNS or IP where our mail comes from.

    My confusion is why does Yahoo and Gmail see our internal LAN AD names when I look at the headers when I sent mail to those domains?

    All that being said, what do I set our PTR record to b/c we are having trouble sending to some domains???

  • #2
    Re: PTR needs FQDN - .com vs .local

    Just set the host name on the Send Connector that matches whatever the DNS record for your IP address is, which should match the PTR - so host.example.com.

    The presence of internal names on the headers is perfectly normal and should not be the cause of problems with delivery of email, because all that external servers are interested in is the server connecting to them.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: PTR needs FQDN - .com vs .local

      thanks for your reply.
      Where can I look that up and be 100% sure?

      When I do a DNS lookup on my server it comes up w/ the local - host.domain.local

      When I do a PTR lookup our provider does not have a PTR record set up for us.

      In our domain host file it says 'mail' as host but then gives an IP address.

      So when you say "host.example.com" do you mean "host" as in the internal computer name? computername.domain.com ?

      Is there anywhere I can test different naming conventions?

      Comment


      • #4
        Re: PTR needs FQDN - .com vs .local

        Internal lookups are useless.
        You need to do lookups using one of the numerous sources on the Internet.

        The Internet doesn't care about the names of your internal servers, so when I am referring to host.example.com that is public names on the Internet, in public DNS records. Nothing to do with your internal DNS which the Internet cannot and should not use.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: PTR needs FQDN - .com vs .local

          I did a tracert from another site to what I think it would be and got a reply from the correct IP.

          the host name is incorrect (it's our ISP) b/c the PTR record has not been created, so I think I've found it.

          thanks for helping clear that up.

          Comment

          Working...
          X