locked
Use public name as DNS suffix RRS feed

  • Question

  •  Working for a Partner customer.

    We're about to receive a new SkypefB environment running SkypefB server 2019. Our internal domain is ad.global and in our current SkypefB server 2015 environment, we're using internal FQDNs for pool, server names etc. For the new one we'd like to use DNS suffix on servers with our public domain (assaabloy.com). Reason is to not require trust of our internal CA and use public certificates internally. Our hosting provider states that this is not a supported solution to use DNS suffixes on Skype-servers not matching our internal domain. Can you please provide an answer if this is supported or not?

    Monday, January 20, 2020 12:46 PM

Answers

  • Hi Sid4563,

    What is the relationship between your Skype for Business server 2015 and Skype for Business server 2019?

    Do you upgrade your SFB 2015 to SFB 2019 or add an SFB 2019 pool in your original environment?

    In my understanding, you can try to add an additional SIP domain in your environment if you want to use the public domain.

    There are several steps you need to do:

    1. Add the new SIP domain to the Topology.

    2. Create DNS records for the new simple URLs, both internal and external.

    3. Request new certificates for the following:

    --Front End Server Certificate (internal)

    --Edge Server Certificate (external)

    --Reverse Proxy Certificate (external)

    4. Run Enable-CsComputer on each pool member and director server. This will configure IIS to accept the new simple URLs.

    You can read the article to learn more about the detailed steps: https://social.technet.microsoft.com/wiki/contents/articles/30621.lync-2013-step-by-step-add-additional-sip-domains-in-existing-deployment.aspx

    In addition, there is a document about Edge server best practice for your reference. You can focus on the paragraph “Multiple SIP domains”. The link is: http://blog.schertz.name/2012/07/lync-edge-server-best-practices/ 

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Tuesday, January 21, 2020 2:35 AM
  • Hi Sid4563,

    If you want to add a new pool in your original environment, you need to use the internal domain first. After you finish the deployment, you can add the public domain as additional SIP domain in your environment as my first reply.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Tuesday, January 21, 2020 9:43 AM

All replies

  • Hi Sid4563,

    What is the relationship between your Skype for Business server 2015 and Skype for Business server 2019?

    Do you upgrade your SFB 2015 to SFB 2019 or add an SFB 2019 pool in your original environment?

    In my understanding, you can try to add an additional SIP domain in your environment if you want to use the public domain.

    There are several steps you need to do:

    1. Add the new SIP domain to the Topology.

    2. Create DNS records for the new simple URLs, both internal and external.

    3. Request new certificates for the following:

    --Front End Server Certificate (internal)

    --Edge Server Certificate (external)

    --Reverse Proxy Certificate (external)

    4. Run Enable-CsComputer on each pool member and director server. This will configure IIS to accept the new simple URLs.

    You can read the article to learn more about the detailed steps: https://social.technet.microsoft.com/wiki/contents/articles/30621.lync-2013-step-by-step-add-additional-sip-domains-in-existing-deployment.aspx

    In addition, there is a document about Edge server best practice for your reference. You can focus on the paragraph “Multiple SIP domains”. The link is: http://blog.schertz.name/2012/07/lync-edge-server-best-practices/ 

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Tuesday, January 21, 2020 2:35 AM
  • Hi Sharon

    New SFB Server 2019

    It’ll be added as a pool and live in coexistence

    Tuesday, January 21, 2020 8:19 AM
  • Hi Sid4563,

    If you want to add a new pool in your original environment, you need to use the internal domain first. After you finish the deployment, you can add the public domain as additional SIP domain in your environment as my first reply.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Tuesday, January 21, 2020 9:43 AM
  • I’m glad that my replies are helpful.

    Here I will provide a brief summary of this post. This will make answer searching in the forum easier.

     

    <Request/Expectation>:

    User environment: Skype for Business server 2015, plan to add a Skype for Business server 2019 pool in the environment.

    Does it support to use DNS suffix on server with user’s public domain in the original environment?

       

    <Suggestions>:

    If you want to add a new pool in your original environment, you need to use the internal domain first. After you finish the deployment, you can add the public domain as additional SIP domain in your environment.

    There are several steps you need to do:

    1. Add the new SIP domain to the Topology.

    2. Create DNS records for the new simple URLs, both internal and external.

    3. Request new certificates for the following:

    --Front End Server Certificate (internal)

    --Edge Server Certificate (external)

    --Reverse Proxy Certificate (external)

    4. Run Enable-CsComputer on each pool member and director server. This will configure IIS to accept the new simple URLs.

        

    <Reference Links>:

    https://social.technet.microsoft.com/wiki/contents/articles/30621.lync-2013-step-by-step-add-additional-sip-domains-in-existing-deployment.aspx

    http://blog.schertz.name/2012/07/lync-edge-server-best-practices/

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, January 23, 2020 8:25 AM