Zonerunner multiple views for same ACL
Hello, If we have multiple views defined as below, the first two views work fine because of different ACL's. If the request(abc1.com) comes from a source in ACL1, it's only looking in view1 and giving SERVFAIL error(expected behavior) . Is there a way it can look in multiple views for the same source? May be including one view in another or Any iRules or Conditions that we can put? View1(order 1): ACL1 Zones: abc.com 1.1.1.1 View2(order 2):ACL2 Zones: abc.com 1.1.1.2 View3(order 3): ACL1 and 2 Zones abc1.com 1.1.1.3
nsupdate to modify zone in specific views.
we have zone name example.com and we have 2 view (external and internal) so in /var/namedb/ we have zone file db.external.example.com and db.internal.example.com . How can we use nsupdate to modify zone in specific views? because we can't seem to specify view in nsupdate script. and we can't specify "zone internal.example.com" in nsupdate script tooF5 DNS combine all zones into one top-level zone
We are migrating our F5 DNS(GTM) towards a new automated setup using AS3, but I noticed we forgot the create a top-level zone in the zone runner configuration. So now all our WideIPs already deployed have their own zone file with the A-records of the pool members. We can create a new top-level zone which should cover all our WideIPs but I am looking for away to transfer all the already existing A-records into this new top-level zone so we delete all the wideip specific zones. Is there an option to re-group all the records into this top-level zone?
ZoneRunner – Zero-downtime migration of records from zone to zone
We are running BIG-IP DNS version 17.5.1.5 and use ZoneRunner for authoritative DNS. Current state: We have a master zone my.com on BIG-IP. In this zone there are multiple records for services under f5.my.com, e.g. r1.f5.my.com, s1.f5.my.com, etc. These are used for WideIP (A/AAAA) and RR responses. We want to introduce a separate authoritative zone f5.my.com (with proper SOA/NS), and then delegate f5.my.com from my.com. Issue/concern: As soon as we create the empty zone f5.my.com on the same BIG-IP, queries for names like r1.f5.my.com stop being answered from the parent zone my.com (ANSWER becomes empty/NODATA), because BIG-IP starts matching the most specific zone. Therefore, creating the new zone first causes an immediate service impact unless all RRsets are already present in f5.my.com at the moment the zone is created. Request: Could you please provide the recommended, supported procedure to migrate RRsets/WideIP-related records from my.com to a new authoritative subzone f5.my.com on BIG-IP DNS without downtime?