Forum Discussion
Jim_Araujo_1061
Nimbostratus
NimbostratusAdding 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.comwip.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.comdb.internal.example.cometc
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.
Brad_ParkerCirrus
I don't believe there is a way to change the behavior, however they are just place holders. The records for wide IPs don't actually have to exist in ZoneRunner to function.
- Jim_Araujo_1061I see, issue is without m anually moving them the External view sees internal wips.
Brad_Parker_139Nacreous
I don't believe there is a way to change the behavior, however they are just place holders. The records for wide IPs don't actually have to exist in ZoneRunner to function.
- Jim_Araujo_1061I see, issue is without m anually moving them the External view sees internal wips.