Announcement

Collapse
No announcement yet.

Receive connnector's FQDN

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

  • Receive connnector's FQDN

    Hello,

    In Exchange 2010, there is (within the receive connector's properties tab), this setting: "Specify the FQDN this connector will provide in response to a HELO/EHLO command".

    Now it is set to "exch1.mydomain.com"

    I am wandering: Should I change it to "mail.domain.com" ?.

    Thanks in advance!
    -
    Madrid (Spain).

  • #2
    Re: Receive connnector's FQDN

    well.. how do you want your mailserver to respond.. ?
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Receive connnector's FQDN

      I really don't know what you mean by that Camel, I do not mean to be rude.

      I am not an expert.

      Thanks though.
      -
      Madrid (Spain).

      Comment


      • #4
        Re: Receive connnector's FQDN

        The response is whatever you want it to be, or more importantly, whatever the sender expects (in case they decide the server is spoofed). Normally this would be the same as one of your public MX records, so mail.domain.com is probably better than server.domain.com
        Tom Jones
        MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
        PhD, MSc, FIAP, MIITT
        IT Trainer / Consultant
        Ossian Ltd
        Scotland

        ** Remember to give credit where credit is due and leave reputation points where appropriate **

        Comment


        • #5
          Re: Receive connnector's FQDN

          Thanks Ossian.

          By default (as I am seeing in some deployments I am making in vmware) the name is Exch-cas-01.domain.com, well, the fqdn of the machine.

          So, would that be worse than setting it to "mail.domain.com" ?
          -
          Madrid (Spain).

          Comment


          • #6
            Re: Receive connnector's FQDN

            I would not say "worse", but in general I would always set an external connector to be a known public DNS name
            Tom Jones
            MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
            PhD, MSc, FIAP, MIITT
            IT Trainer / Consultant
            Ossian Ltd
            Scotland

            ** Remember to give credit where credit is due and leave reputation points where appropriate **

            Comment


            • #7
              Re: Receive connnector's FQDN

              The receive connector FQDN should be either
              a. The server's real name
              b. The server's NETBIOS name
              c. Blank.

              Setting it to the external DNS of the server is pointless and can actually cause email delivery.

              The only people who set it are those that want to pass the dumb tests at mxtoolbox and the like, which presume that the inbound banner is the same as the outbound banner (which it is not).

              Therefore leave it as it is - with the server's real FQDN.

              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


              • #8
                Re: Receive connnector's FQDN

                Thanks both.

                So...what is the purpose of that field?

                I know that the purpose of the Sending connector's fqdn filed is for security checks, but not about this one (the receive connector's fqdn helo/ehlo)

                Again: Thanks!
                -
                Madrid (Spain).

                Comment


                • #9
                  Re: Receive connnector's FQDN

                  If you have multiple connectors, then you can set the FQDN on to additional connectors so they can be tracked through the logs.

                  The default connector needs to be configured as I have outlined.

                  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


                  • #10
                    Re: Receive connnector's FQDN

                    Thanks Sembee.

                    I meant to ask what is the purpose of that receive connector's fqdn , regarless of the number of them that there are implemented.
                    -
                    Madrid (Spain).

                    Comment


                    • #11
                      Re: Receive connnector's FQDN

                      Two purposes.
                      1. For identification of the inbound connector used.
                      2. It is used by Exchange to match an SSL certificate.

                      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


                      • #12
                        Re: Receive connnector's FQDN

                        Wow. Thanks Sembee! .
                        -
                        Madrid (Spain).

                        Comment

                        Working...
                        X