Forum Discussion

duckngooser's avatar
duckngooser
Icon for Nimbostratus rankNimbostratus
Jun 16, 2018

How to configure GTM with DNS at Network Solutions

We currently use Network Solutions for our internet DNS. How do we go about setting up GTM when DNS requests don't actually come to our data centers where the F5's live?

 

application delivery
BIG-IP DNS
LTM
security
  • AceDawg_204810's avatar
    AceDawg_204810
    Icon for Cirrus rankCirrus
    Jun 16, 2018

    When setting up GTM with an existing DNS infrastructure, the location of the DNS servers is not relevant (on prem, off prem, cloud). What is relevant is the proper configuration of the Network Solutions DNS to reflect the existence of your GTM infrastructure. There are 4 basic steps that need to be considered in the overarching setup:

     

    1. Create a sub domain on your existing DNS setup (e.g. gtm.domain.com)
    2. Configure the existing DNS making GTM server(s) authoritative over the new sub domain
    3. Any DNS resource managed by GTM will be declared by CNAME (name.domain.com in CNAME name.gtm.domain.com)
    4. Configure a wide ip in GTM (name.gtm.domain.com) with the appropriate pools, load balancing methods, etc. to return responses that reflect the organization’s requirements
    • duckngooser's avatar
      duckngooser
      Icon for Nimbostratus rankNimbostratus
      Jun 17, 2018

      So if the current site is , to accomplish this without changing the name of the site and cert on the site to , I'd just need to set example.com to authoritative on GTM and configure the current DNS to point towards GTM as the authoritative source?

       

    • AceDawg_204810's avatar
      AceDawg_204810
      Icon for Cirrus rankCirrus
      Jun 17, 2018

      That is correct.

       

      1. create a sub domain called gtm.example.com on the network solutions dns server.

      2. create a nameserver record on network solutions dns (gtm.example.com in ns gtmserver.example.com)

         

      3. create a cname record for on network solutions dns ( in cname )

         

      4. create wideip configuration on gtmserver.example.com for

         

      Client requests set the http host header to so there won't be a ssl cert error. DNS will simply provide resolution for purposes of ip routing.

       

  • AceDawg1's avatar
    AceDawg1
    Icon for Nimbostratus rankNimbostratus
    Jun 16, 2018

    When setting up GTM with an existing DNS infrastructure, the location of the DNS servers is not relevant (on prem, off prem, cloud). What is relevant is the proper configuration of the Network Solutions DNS to reflect the existence of your GTM infrastructure. There are 4 basic steps that need to be considered in the overarching setup:

     

    1. Create a sub domain on your existing DNS setup (e.g. gtm.domain.com)
    2. Configure the existing DNS making GTM server(s) authoritative over the new sub domain
    3. Any DNS resource managed by GTM will be declared by CNAME (name.domain.com in CNAME name.gtm.domain.com)
    4. Configure a wide ip in GTM (name.gtm.domain.com) with the appropriate pools, load balancing methods, etc. to return responses that reflect the organization’s requirements
    • duckngooser's avatar
      duckngooser
      Icon for Nimbostratus rankNimbostratus
      Jun 17, 2018

      So if the current site is , to accomplish this without changing the name of the site and cert on the site to , I'd just need to set example.com to authoritative on GTM and configure the current DNS to point towards GTM as the authoritative source?

       

    • AceDawg1's avatar
      AceDawg1
      Icon for Nimbostratus rankNimbostratus
      Jun 17, 2018

      That is correct.

       

      1. create a sub domain called gtm.example.com on the network solutions dns server.

      2. create a nameserver record on network solutions dns (gtm.example.com in ns gtmserver.example.com)

         

      3. create a cname record for on network solutions dns ( in cname )

         

      4. create wideip configuration on gtmserver.example.com for

         

      Client requests set the http host header to so there won't be a ssl cert error. DNS will simply provide resolution for purposes of ip routing.