Adding a new WIP and having it placed in the correct Zone
I have a scenario where when I create a new Wide IP, it is not being put into the correct zone file. For example. 3 zones: example.com wip.example.com xwip.example.com When I create a new Wide IP, like test.wip.example.com, it is being placed into the example.com zone file!!. Is that the correct behavior? It gets more complicated as I also have 2 different views. External Internal which have their own zone files for each of the 3 zones. db.external.example.com db.internal.example.com etc Unfortuntely everything is being placed into the db.external.example.com file no matter what type of record it is...I have to manually move it. Is there a better way to do this? Also, does anyone know what the GTM uses to make it's decision on where to put new WIPs into what zone files? I know ZoneRunner is involved in that part, but I'm not sure how it is making it's zone file destiantion decision.
pycontrol Zone::add_zone_text
I am attempting to add Zones under Zone Runner using pycontrol, where my input is a csv file of zone records. The idea is to automate entering the zones using a script. The add_zone_text function should do the job, however I cannot figure out what the parameter's text format is supposed to be like. Can someone provide a full example? (e.g. text = ['SOA ... NS ...',] or however it is supposed to be.)
Zone-transfer to a Wide-IP and iRules
Hi, how's it going? I've deployed two DNS on different DC's (a classical 2 DC's internally interconnected, so BIG-IP A can reach what's behind BIG-IP B and viceversa). All wide-IP's resolve to a public IP address. This is OK, but there are internal client who query for those names, but need to receive an internal address. This is also no problem, can be solved using an iRule for internal addresses. Now, the problem is here: an interesting number of these internal clients reside on a geographically remote location, but need to be resolved to this internal address. Again, this wouldn't be a problem for the F5 configuration, but we don't want to have a super high traffic through the MPLS (or whatever it is that interconnect the remote locations). Each geographic zone has a local AD-DNS, and I've been thinking that, maybe, they could do an AXFR to the BIG-IP, so to reduce the traffic and confine it to each place. So: Is it posible to perform an AXFR for the wide-IP's? (Not for the names configured in bind, not for the names behind the F5). If it indeed is, how could I configure the F5's so they reply with an internal zone? Would we be better off using the AD-DNS cache instead? Thanks in advance!