Changes are used to make an atomic change to the ResourceRecordSets . The additions and deletions all take effect at the same time. When making changes, you can delete and add the SOA resource record to update the serial number for the zone to ensure that if multiple Changes are submitted that they happen in the intended order and do not conflict.

For a list of methods for this resource, see the end of this page.

Resource representations

An atomic update to a collection of ResourceRecordSets .

{
  "kind": "dns#change",
  "additions": [
    resourceRecordSets Resource
  ],
  "deletions": [
    resourceRecordSets Resource
  ],
  "startTime": string,
  "id": string,
  "status": string
}

Methods

The following are valid Changes methods:

create

Atomically updates the ResourceRecordSet collection. This method can include both additions and deletions. If you need to update a resource record, you send the deletion and addition of the record in the same request. As a best practice to prevent collisions with other changes, you should increment the serial number of your SOA record with each request to this method by sending a deletion and addition of the SOA record with your other changes.

get

Fetches the representation of an existing Change . You can monitor the status of changes by using this method and checking the status field in the response.

list

Enumerates the list of Changes to a ResourceRecordSet collection. The status of the changes can be determined by examining the status field. This method allows you to see a historical record of all changes made to the resource record sets for the managed zone. For more information, see Monitoring changes .