locked
Configure DNS for your Pool RRS feed

  • Question

  • Good morning all,

    Page 12 of the OCS Deployment Guide has the DNS configurations steps which is to setup the Client DNS queries (middle of the page).

    This is very similar to what we did for LCS 2005.

    So in DNS I know have two entries for the _sipinternaltls._tcp.domain - for internal TLS connections.  One for my LCS pool and one for my OCS pool.

    How are the clients going to differieniate between the two?  Should the LCS and OCS pool be named the same?

    Friday, May 18, 2007 4:39 PM

Answers

  • The clients will not be able to differentiate between the two.  What will most likely happen is that the DNS server will notice that the two SRV records have the same name and will serve them up in a round robin fashion, where it alternates between the two entries in response to the clients.

     

    If you are going to use autodiscover with both versions running you should point the SRV record to the OCS pool.  Assuming both LCS and OCS are in the same forest, when an LCS client connects to the OCS pool it will act as a director and point the client to the LCS pool.  You should not name the two pools the same name (this wouldn't work anyway since there would be a conflicting object in AD).


    Z

    Friday, May 18, 2007 4:46 PM
    Moderator

All replies

  • The clients will not be able to differentiate between the two.  What will most likely happen is that the DNS server will notice that the two SRV records have the same name and will serve them up in a round robin fashion, where it alternates between the two entries in response to the clients.

     

    If you are going to use autodiscover with both versions running you should point the SRV record to the OCS pool.  Assuming both LCS and OCS are in the same forest, when an LCS client connects to the OCS pool it will act as a director and point the client to the LCS pool.  You should not name the two pools the same name (this wouldn't work anyway since there would be a conflicting object in AD).


    Z

    Friday, May 18, 2007 4:46 PM
    Moderator
  • You should not use the same pool names, you will have to create a new pool name which means new or additional DNS SRV and Host records.  The FE server or director if you have one will do the authentication, so if users are moved to the new server the infrastructure will know about it.

     

    Byron

    Tuesday, May 22, 2007 7:33 PM