Forum Discussion

Amanpreet_Singh's avatar
Amanpreet_Singh
Icon for Cirrostratus rankCirrostratus
Nov 19, 2015

WideIP vs Zone in zonerunner

Hello guys,

I have recently moved into the project to support existing setup of GTM/LTM running to Internet based applications. While looking into the setup I stumble with some specific things which I could not get hold on-

  • On GTM, they have a wide IP created for site1.example.mydomain.com. Along with that, they also have Master Zone file in Zonerunner for site1.example.mydomain.com. Why are they using both? Is it recommended?
  • On GTM, in Zonerunner, they are creating different zone files for each URL. For Ex- Different Master-zone for site1.example.mydomain.com, site2.example.mydomain.com, site3.example.mydomain.com. Although I can also see a zone file for - example.mydomain.com. Why can't we use example.mydomain.com only rather than creating separate zone file for site1,site2,site3? Are there any pros and cons?

To me, it looks like we are using both wideIP and BIND(zonerunner) for the same URL. The listeners on GTM are-

  • 10.x.x.x 10.x.x.x 255.255.255.0
    internal
    traffic-group-local-only Common
  • 200.x.x.x 200.x.x.x 255.255.254.0
    external
    traffic-group-local-only Common

Kindly help in understanding this situation.

Thanks and Regards,

2 Replies

  • Hi,

     

    • wideIPs are GTM objects.
    • zonerunner is the local BIND configuration tool.

    every time you create a WideIP in GTM:

     

    • if zone of wideIP does not exist in BIND, zone runner create it.
    • zonerunner create in BIND one A record of wideIP for every wideIP pool members.

    if GTM pool fallback LB method is "return to DNS" and both preferred and alternate method does not select a pool member (all members are down or LB methods cannot chose one), BIND will answer instead of GTM.

     

  • Hi ,

     

    Adding to Stanislas For the part which you asked that why they are creating multiple zones in case of only one .

     

    That depends on the you: to configure sub-domains you can either delegate the sub-domain have soa record, NS record and it's glue record or create sub-domain in the master zone itself and in this you define master and sub domain configuration in single file.

     

    one of the advantage of this will if you do some change and need to reload the zone you can do that separately instead of reloading all the zones at same time. There will other pros/cons as well others can chime in .