Forum Discussion

Keith_Richards_'s avatar
Keith_Richards_
Icon for Nimbostratus rankNimbostratus
Feb 07, 2008

Right way of configuring GTM and parent DNS?

The training manual has this to say about the steps to migrating to a system where the GTM will only receive requests for wide IPs within a domain.

 

 

Configure the existing name databases on the current DNS servers e.g. ns1.ispX.com and ns2.ispX.com that the Wide IPs are delegated to the GTM System. Note that the GTM System should be configured to resolve the wide IP prior to implementing this change in the current system.

 

 

Example database prior to delegation:

 

 

www.domain.com. IN A 200.10.10.10

 

www.domain.com. IN A 150.10.10.10

 

 

Example database after delegation:

 

 

wip.domain.com. IN NS gtm1.wip.domain.com.

 

wip.domain.com. IN NS gtm2.wip.domain.com.

 

gtm1.wip.domain.com. IN A 200.10.10.53

 

gtm2.wip.domain.com. IN A 150.10.10.54

 

www.domain.com. IN CNAME www.wip.domain.com.

 

 

There is another way that would work:

 

 

www.domain.com. IN NS gtm1.domain.com.

 

www.domain.com. IN NS gtm2.domain.com.

 

gtm1.domain.com. IN A 200.10.10.53

 

gtm2.domain.com. IN A 150.10.10.54

 

 

This approach defines the www.domain.com as being a sub domain of domain.com, and the GTMs won’t care how they received the request for www.domain.com as long as the WIP exists then they should respond. The down side to this approach is that any further hosts which will be hosted on GTM will also require two NS record lines whereas the first approach just needs the CNAME entry.

 

 

My question to you all is ‘which way is right?’ and is the latter approach actually wrong?

 

 

 

 

  • The first method is correct. The second method can be made to work but you must create SOA and full domain records on the GTM or you run the risk of having customer issues. Remember, GTM will fall through to standard DNS and must have the proper structure to respond appropriately to resolvers.

     

  • Deb_Allen_18's avatar
    Deb_Allen_18
    Historic F5 Account
    Both are actually valid approaches that are widely used. GTM automatically creates the required zone file including the appropriate SOA info when any name is added as a WideIP.

     

     

    However, F5's recommended best practice is actually the first: To use a CNAME in your primary DNS that points to a name in a subdomain delegated to GTM. That way you are delegating only the name-to-IP relationship, and the parent zone configuration is still authoritative for MX etc.

     

     

    HTH

     

    /deb