Announcement

Collapse
No announcement yet.

Autodiscover in Exchange 2010

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

  • Autodiscover in Exchange 2010

    Hello,

    Not long ago I posted a somewhat similar question. I am all mixed up, sorry about it.

    If I got it right:

    From my outlook 2010 in the WAN , when I type [email protected] , the Autodiscover feature will look up "autodiscover.domain.com" in a Public DNS Server.

    Once it gets the ip from "autodiscover.domain.com" , it will go to the router that posseses this ip, and, behind this router, there will be an Exchange Server.

    In this Exchange server , must there be a certificate whose common name is "autodiscover.domain.com" ?

    I am sorry but I am not sure if this is the process to make it work.

    Thanks in advance.


    -
    Madrid (Spain).

  • #2
    What is your question?
    You need to have Autodiscover.example.com on the SSL certificate for the client to find the information correctly.
    If you cannot do that, then you need to configure an SRV record instead, ensuring that Autodiscover.example.com does NOT resolve externally.

    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
      Thanks Seembe.

      You explained it very nicely, thanks!
      Last edited by loureed4; 8th June 2015, 19:01.
      -
      Madrid (Spain).

      Comment


      • #4
        Do I need a public dns record called: "autodiscover.domain.com" for this to work ?
        -
        Madrid (Spain).

        Comment


        • #5
          Autodiscover - Might be worth a look.

          DNS Record for autodiscover

          Autodiscover Record and Why it is Needed. - Thought this was quite good plus some relevant links at the bottom of the page.

          How's the study going Luis? Well I hope.

          1 1 was a racehorse.
          2 2 was 1 2.
          1 1 1 1 race 1 day,
          2 2 1 1 2

          Comment


          • #6
            My question about the need of a public dns record called "autodiscover.domain.com" was pretty silly, for I had studied it was needed.

            I am just a bit mixed up because when configuring Outlook anywhere, I read in some places the need to go into the outlook profile and type in "mail.domain.com" and "msstd:mail.domain.com" , in the Exchange proxy properties, while I thought autodiscover was all it was necessary.

            I mean:

            1. Public DNS record "mail.domain.com"
            2. 443 open port (https) in firewall, too obvious.
            3. Certificate installed within the CAS Exchange server, with common name "mail.domain.com" and alternative names "autodiscover.domain.com, mailserver.domain.com, mailserver" .
            4. NTLM or Basic authentication for Outllok anywhere, depending on whether the firewall can handle NTLM authenticacion Delegation.
            5. Private cname dns record "autodiscover.domain.com" and "mail.domain.com", pretty obvious too.

            I have read several documents, so far, but some times I read the "msstd:mail.domain.com" thing.

            Biggles77, my sutdies are going well, many stuff to study, overwhelming!
            -
            Madrid (Spain).

            Comment


            • #7
              Originally posted by biggles77 View Post
              Autodiscover - Might be worth a look.

              DNS Record for autodiscover

              Autodiscover Record and Why it is Needed. - Thought this was quite good plus some relevant links at the bottom of the page.

              How's the study going Luis? Well I hope.

              By the way: THANKS A LOT !!
              -
              Madrid (Spain).

              Comment

              Working...
              X