Is there soamname override field for zone_auth in WAPI

[#1]

Looking for soamname override (similar to API) field at zone level (zone_auth) in WAPI. Couldn't find in the WAPI document.

[#2]

You are correct. it is in the PAPI, but not available in the WAPI.

Open a bug with support.

[#3]

Nice finding Please keep this thread updated

[#4 · Accepted solution]

Found similar in old version of WAPI documentation and it worked. As per infoblox they corrected the documentation 6.12.0 and 6.12.18.

soa_mname

The SOA mname value for this zone. The Infoblox appliance allows you to change the name of the primary server on the SOA record that is automatically created when you initially configure a zone. Use this method to change the name of the primary server on the SOA record. For example, you may want to hide the primary server for a zone. If your device is named dns1.zone.tld, and for security reasons, you want to show a secondary server called dns2.zone.tld as the primary server. To do so, you would go to dns1.zone.tld zone (being the real primary) and change the primary server on the SOA to dns2.zone.tld to hide the true identity of the real primary server. This value can be in unicode format.

[#5]

hoi how does this looks like in wapi call iam newbie in this field in like tu update the mnames of 1000 domains with other name servers how will this scrips looks like? 

Chris

[#6]

You need to send a PUT request against the zone's '_ref' instance that contains a body with the appropriate structure for `member_soa_mnames`. Note that the parameter is plural. It expects an array with a value for each primary nameserver associated with the zone (even if you only have one primary). It might look something like this.

PUT https://gm.example.com/wapi/v2.10/zone_auth/xxxxxxxxxxxxxxxxxxxxx:example.net/default

{
  "member_soa_mnames": [
    {
      "mname": "new-ns1.example.net",
      "grid_primary": "ns1.example.net"
    },
    {
      "mname": "new-ns2.example.net",
      "grid_primary": "ns2.example.net"
    }
  ]
}