locked
DNS records that Im confused about RRS feed

  • Question

  • Hi there,

    Just want to clarify the DNS requirements...use CNAMES when using multiple sipdomains or not...

    Reverse Proxy (VIP):
    - webext.company.com (external web services)
    - wac.company.com (Points towards Office Online Server/servers)
    - meet.company.com (configured to be (meet.company.com/company, meet.company.com/companyB...)
    - dialin.company.com
    - lyncdiscover.company.com
    - lyncdiscover.companyB.com
    - lyncdiscover.companyC.com

    Edge pool 2 servers (DNS round robin):
    access.company.com (A record points towards each edge server = 2 dns records total)
    webconf.company.com (A record points towards each edge server = 2 dns records total)
    av
    .company.com (points towards each edge server = 2 dns records)

    External:
    sip.company.com -> A records towars each edge access server OR a single CNAME using access.company.com?
    sip.companyB.com -> 2 x A records towards each edge access server OR a single CNAME using access.company.com?
    sip.companyB.com -> 2 x A records towards each edge access server OR a single CNAME using access.company.com?

    So either each sip.<domain> has two A records (one for each access edge ip) or a single CNAME record pointing towards access.company.com?

    for the SRV records it should points towards sip.<domain> right?

    Internal:
    same question for the internal sip.company.com, sip.companyB.com, sip.companyC.com...shall one create 4 A records for each name towards our 4 Front-End server FQDN's or a single CNAME for each domain pointing towards the pool name, pool01.company.com?

    Saves a bit of DNS records using CNAMES but is it supported or best practice?

    Any issues with the common name in the certificates?




    • Edited by [zid] Wednesday, November 22, 2017 10:48 PM
    Wednesday, November 22, 2017 10:35 PM

Answers

  • Hi [zid],

     

    Do you want to achieve the DNS for Disaster Recovery?

    If so you must be using a DNS provider that supports GeoDNS and create CNAME to achieve it.

    You could refer to the following link

    https://technet.microsoft.com/en-us/library/gg398758(v=ocs.15).aspx#Configuring the domain name system (DNS) for Disaster Recovery

     

    If you just want to achieve DNS loadbalance,you could create Sip.company.com to point different IP of servers.

    https://technet.microsoft.com/en-us/library/gg398201(v=ocs.15).aspx#IMPORTANT: Edge Server Network Adapter Requirements


    Regards,

    Leon Lu


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

    Thursday, November 23, 2017 8:09 AM

All replies

  • Hi [zid],

     

    Do you want to achieve the DNS for Disaster Recovery?

    If so you must be using a DNS provider that supports GeoDNS and create CNAME to achieve it.

    You could refer to the following link

    https://technet.microsoft.com/en-us/library/gg398758(v=ocs.15).aspx#Configuring the domain name system (DNS) for Disaster Recovery

     

    If you just want to achieve DNS loadbalance,you could create Sip.company.com to point different IP of servers.

    https://technet.microsoft.com/en-us/library/gg398201(v=ocs.15).aspx#IMPORTANT: Edge Server Network Adapter Requirements


    Regards,

    Leon Lu


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

    Thursday, November 23, 2017 8:09 AM
  • Are there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who has similar issue.

    Regards,

    Leon Lu


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

    Monday, November 27, 2017 11:06 AM