Table of Contents

• Getting Started
  • Helpful Background Information
  • Prerequisites
  • External Dependencies
  • Adapters
  • How to Install
  • Testing
• Using this Workflow Project
  • Assign Next IP - Infoblox
  • Create DNS A Record - Infoblox
  • Create DNS CNAME Record - Infoblox
  • Create DNS Fixed Address Record - Infoblox
  • Create DNS NS Record - Infoblox
  • Create DNS PTR Record - Infoblox
  • Create Network - Infoblox
  • Create Network Container - Infoblox
  • Delete DNS A Record - Infoblox
  • Delete DNS CNAME Record - Infoblox
  • Delete DNS Fixed Address Record - Infoblox
  • Delete DNS NS Record - Infoblox
  • Delete DNS PTR Record - Infoblox
  • Delete Network - Infoblox
  • Delete Network Container - Infoblox
  • Modify DNS A Record - Infoblox
  • Modify DNS CNAME Record - Infoblox
  • Modify DNS Fixed Address Record - Infoblox
  • Modify DNS NS Record - Infoblox
  • Modify DNS PTR Record - Infoblox
• Additional Information
  • Support

Getting Started

This section is helpful for deployments as it provides you with pertinent information on prerequisites and properties.

Helpful Background Information

Workflows often include logic that varies from business to business. As a result, we often find that our Workflow Projects are more useful as modular components that can be incorporated into a larger process. In addition, they often can add value as a learning tool on how we integrate with other systems and how we do things within the Itential Automation Platform.

While these can be utilized, you may find more value in using them as a starting point to build around.

Prerequisites

Itential Workflow Projects are built and tested on particular versions of IAP. In addition, Workflow Projects are often dependent on external systems and as such, these Workflow Projects will have dependencies on these other systems. This version of Infoblox - DDI - REST has been tested with:

• IAP 2023.2

External Dependencies

Adapters

How to Install

To install the Workflow Project:

• Verify you are running a supported version of the Itential Automation Platform (IAP) as listed above in the Supported IAP Versions section in order to install the Example Project.
• Import the Example Project in Admin Essentials.

Testing

Cypress is generally used to test all Itential Example Projects. While Cypress is an opensource tool, at Itential we have internal libraries that have been built around Cypress to allow us to test with a deployed IAP.

When certifying our Example Projects for a release of IAP we run these tests against the particular version of IAP and create a release branch in GitLab. If you do not see the Example Project available in your version of IAP please contact Itential.

While Itential tests this Example Project and its capabilities, it is often the case the customer environments offer their own unique circumstances. Therefore, it is our recommendation that you deploy this Example Project into a development/testing environment in which you can test the Example Project.

Using this Workflow Project

Workflow Projects contain 1 or more workflows. Each of these workflows have different inputs and outputs.

Assign Next IP - Infoblox

A modular workflow that automates assigning the next available IP from a network in Infoblox.

Capabilities include:

• The workflow is used to assign next available IP in Infoblox

Entry Point IAP Component

The primary IAP component to run Assign Next IP - Infoblox is listed below:

Inputs

The following table lists the inputs for Assign Next IP - Infoblox:

10.0.0.0/24

foo

Testing

Infoblox

Outputs

The following table lists the outputs for Assign Next IP - Infoblox:

{
  "assignedIP": "10.0.0.2",
  "hostName": "foo",
  "hostKey": {
    "icode": "AD.201",
    "response": {
      "result": "record:host/ZG5zLmhvc3QkLm5vbl9ETlNfaG9zdF9yb290LjAuMTY5ODMzMDgyNDc3NC5mb28:foo/%20"
    }
  }
}

{
  "icode": "AD.999",
  "IAPerror": {
    "origin": "Infoblox-adapter-assignNextIP2",
    "displayString": "Network not found",
    "recommendation": "Make sure the network exists"
  }
}

Query Output

The following items show how to query successful results from the output of Assign Next IP - Infoblox:

Next assigned IP

assignedNextIp.assignedIP

The following items show how to query failure results from the output of Assign Next IP - Infoblox:

Error Response Message

infobloxError.IAPerror.displayString

Example Inputs and Outputs

Example 1

Input:

{
  "networkIP": "10.0.0.0/24",
  "hostName": "foo",
  "comment": "Testing",
  "adapterId": "Infoblox"
} 

Output:

{
  "assignedNextIp": {
    "assignedIP": "10.0.0.2",
    "hostName": "foo",
    "hostKey": {
      "icode": "AD.201",
      "response": {
        "result": "record:host/ZG5zLmhvc3QkLm5vbl9ETlNfaG9zdF9yb290LjAuMTY5ODMzMDgyNDc3NC5mb28:foo/%20"
      }
    }
  }
} 

Example 2

Input:

{
  "networkIP": "1.1.1.1",
  "hostName": "bar",
  "comment": "test",
  "adapterId": "Infoblox"
} 

Output:

{
  "assignedNextIp": null,
  "infobloxError": {
    "icode": "AD.999",
    "IAPerror": {
      "origin": "Infoblox-adapter-assignNextIP2",
      "displayString": "Network not found",
      "recommendation": "Make sure the network exists"
    }
  }
} 

API Links

Create DNS A Record - Infoblox

A modular workflow that automates creating a DNS A record in Infoblox.

Capabilities include:

• The workflow is used to create an A record in Infoblox

Entry Point IAP Component

The primary IAP component to run Create DNS A Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Create DNS A Record - Infoblox:

test.lab.itential.com

1.1.1.1

default

Infoblox

Outputs

The following table lists the outputs for Create DNS A Record - Infoblox:

{
  "icode": "AD.201",
  "response": "record:a/ZG5zLmJpbmRfYSQuX2RlZmF1bHQuY29tLml0ZW50aWFsLmxhYix0ZXN0LDEuMS4xLjE:test.lab.itential.com/default"
}

{
  "icode": "AD.500",
  "IAPerror": {
    "origin": "Infoblox-connectorRest-handleEndResponse",
    "displayString": "Error 400 received on request",
    "recommendation": "Verify the request is accurate via debug logs and postman",
    "code": 400,
    "raw_response": {
      "status": "success",
      "code": 400,
      "response": {
        "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
        "code": "Client.Ibap.Data.Conflict",
        "text": "The action is not allowed. A parent was not found."
      }
    }
  },
  "response": {
    "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
    "code": "Client.Ibap.Data.Conflict",
    "text": "The action is not allowed. A parent was not found."
  }
}

Query Output

The following items show how to query successful results from the output of Create DNS A Record - Infoblox:

Create A Record Request Result

createdARecord.response

The following items show how to query failure results from the output of Create DNS A Record - Infoblox:

Error Response Message

infobloxError.response.text

Example Inputs and Outputs

Example 1

Input:

{
  "hostname": "test.lab.itential.com",
  "ipAddress": "1.1.1.1",
  "dnsView": "default",
  "adapterId": "Infoblox"
} 

Output:

{
  "createdARecord": {
    "icode": "AD.201",
    "response": "record:a/ZG5zLmJpbmRfYSQuX2RlZmF1bHQuY29tLml0ZW50aWFsLmxhYix0ZXN0LDEuMS4xLjE:test.lab.itential.com/default"
  }
} 

Example 2

Input:

{
  "hostname": "foo.bar",
  "ipAddress": "1.1.1.1",
  "dnsView": "default",
  "adapterId": "Infoblox"
} 

Output:

{
  "createdARecord": null,
  "infobloxError": {
    "icode": "AD.500",
    "IAPerror": {
      "origin": "Infoblox-connectorRest-handleEndResponse",
      "displayString": "Error 400 received on request",
      "recommendation": "Verify the request is accurate via debug logs and postman",
      "code": 400,
      "raw_response": {
        "status": "success",
        "code": 400,
        "response": {
          "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
          "code": "Client.Ibap.Data.Conflict",
          "text": "The action is not allowed. A parent was not found."
        }
      }
    },
    "response": {
      "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
      "code": "Client.Ibap.Data.Conflict",
      "text": "The action is not allowed. A parent was not found."
    }
  }
} 

API Links

Create DNS CNAME Record - Infoblox

A modular workflow that automates creating a DNS CNAME record in Infoblox.

Capabilities include:

• The workflow is used to create a CNAME record in Infoblox

Entry Point IAP Component

The primary IAP component to run Create DNS CNAME Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Create DNS CNAME Record - Infoblox:

cnametest.demo.lab.itential.com

demo.lab.itential.com

default

Infoblox

Outputs

The following table lists the outputs for Create DNS CNAME Record - Infoblox:

{
  "icode": "AD.201",
  "response": "record:cname/ZG5zLmJpbmRfY25hbWUkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuZGVtby5jbmFtZXRlc3Q:cnametest.demo.lab.itential.com/default"
}

{
  "icode": "AD.500",
  "IAPerror": {
    "origin": "Infoblox-connectorRest-handleEndResponse",
    "displayString": "Error 400 received on request",
    "recommendation": "Verify the request is accurate via debug logs and postman",
    "code": 400,
    "raw_response": {
      "status": "success",
      "code": 400,
      "response": {
        "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
        "code": "Client.Ibap.Data.Conflict",
        "text": "The action is not allowed. A parent was not found."
      }
    }
  },
  "response": {
    "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
    "code": "Client.Ibap.Data.Conflict",
    "text": "The action is not allowed. A parent was not found."
  }
}

Query Output

The following items show how to query successful results from the output of Create DNS CNAME Record - Infoblox:

Create CNAME Record Request Result

cnameRecord.response

The following items show how to query failure results from the output of Create DNS CNAME Record - Infoblox:

Error Response Message

infobloxError.response.text

Example Inputs and Outputs

Example 1

Input:

{
  "adapterId": "Infoblox",
  "dnsView": "default",
  "aliasName": "cnametest.demo.lab.itential.com",
  "canonicalName": "demo.lab.itential.com"
} 

Output:

{
  "cnameRecord": {
    "icode": "AD.201",
    "response": "record:cname/ZG5zLmJpbmRfY25hbWUkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuZGVtby5jbmFtZXRlc3Q:cnametest.demo.lab.itential.com/default"
  }
} 

Example 2

Input:

{
  "adapterId": "Infoblox",
  "dnsView": "default",
  "aliasName": "cnametest.demo.info.com",
  "canonicalName": "demo.info.com"
} 

Output:

{
  "cnameRecord": null,
  "infobloxError": {
    "icode": "AD.500",
    "IAPerror": {
      "origin": "Infoblox-connectorRest-handleEndResponse",
      "displayString": "Error 400 received on request",
      "recommendation": "Verify the request is accurate via debug logs and postman",
      "code": 400,
      "raw_response": {
        "status": "success",
        "code": 400,
        "response": {
          "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
          "code": "Client.Ibap.Data.Conflict",
          "text": "The action is not allowed. A parent was not found."
        }
      }
    },
    "response": {
      "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
      "code": "Client.Ibap.Data.Conflict",
      "text": "The action is not allowed. A parent was not found."
    }
  }
} 

API Links

Create DNS Fixed Address Record - Infoblox

A modular workflow that automates creating a fixed address in Infoblox. A fixed address is a specific IP address that a DHCP server always assigns when a lease request comes from a particular MAC address of the client.

Capabilities include:

• The workflow is used to create a Fixed Address record in Infoblox

Entry Point IAP Component

The primary IAP component to run Create DNS Fixed Address Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Create DNS Fixed Address Record - Infoblox:

10.0.0.1

aa:bb:cc:45:67:45

Infoblox

Outputs

The following table lists the outputs for Create DNS Fixed Address Record - Infoblox:

{
  "icode": "AD.201",
  "response": "fixedaddress/ZG5zLmZpeGVkX2FkZHJlc3MkMTAuMC4wLjEuMC4u:10.0.0.1/default"
}

{
  "icode": "AD.500",
  "IAPerror": {
    "origin": "Infoblox-connectorRest-handleEndResponse",
    "displayString": "Error 400 received on request",
    "recommendation": "Verify the request is accurate via debug logs and postman",
    "code": 400,
    "raw_response": {
      "status": "success",
      "code": 400,
      "response": {
        "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Cannot find the parent network for the fixed address 10.0.0.1.)",
        "code": "Client.Ibap.Data.Conflict",
        "text": "Cannot find the parent network for the fixed address 10.0.0.1."
      }
    }
  },
  "response": {
    "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Cannot find the parent network for the fixed address 10.0.0.1.)",
    "code": "Client.Ibap.Data.Conflict",
    "text": "Cannot find the parent network for the fixed address 10.0.0.1."
  }
}

Query Output

The following items show how to query successful results from the output of Create DNS Fixed Address Record - Infoblox:

Create Fixed Address Record Request Result

fixedAddressRecord.response

The following items show how to query failure results from the output of Create DNS Fixed Address Record - Infoblox:

Error Response Message

infobloxError.response.text

Example Inputs and Outputs

Example 1

Input:

{
  "adapterId": "Infoblox",
  "ipAddress": "10.0.0.1",
  "macAddress": "aa:bb:cc:45:67:45"
} 

Output:

{
  "fixedAddressRecord": {
    "icode": "AD.201",
    "response": "fixedaddress/ZG5zLmZpeGVkX2FkZHJlc3MkMTAuMC4wLjEuMC4u:10.0.0.1/default"
  }
} 

Example 2

Input:

{
  "adapterId": "Infoblox",
  "ipAddress": "10.0.0.1",
  "macAddress": "aa:bb:cc:45:67:45"
} 

Output:

{
  "fixedAddressRecord": null,
  "infobloxError": {
    "icode": "AD.500",
    "IAPerror": {
      "origin": "Infoblox-connectorRest-handleEndResponse",
      "displayString": "Error 400 received on request",
      "recommendation": "Verify the request is accurate via debug logs and postman",
      "code": 400,
      "raw_response": {
        "status": "success",
        "code": 400,
        "response": {
          "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Cannot find the parent network for the fixed address 10.0.0.1.)",
          "code": "Client.Ibap.Data.Conflict",
          "text": "Cannot find the parent network for the fixed address 10.0.0.1."
        }
      }
    },
    "response": {
      "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Cannot find the parent network for the fixed address 10.0.0.1.)",
      "code": "Client.Ibap.Data.Conflict",
      "text": "Cannot find the parent network for the fixed address 10.0.0.1."
    }
  }
} 

API Links

Create DNS NS Record - Infoblox

A modular workflow that automates creating a DNS NS record in Infoblox.

Capabilities include:

• The workflow is used to create a NS record in Infoblox

Entry Point IAP Component

The primary IAP component to run Create DNS NS Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Create DNS NS Record - Infoblox:

lab.itential.com

infoblox.localdomain

[
  {
    "address": "192.168.10.1"
  }
]

default

Infoblox

Outputs

The following table lists the outputs for Create DNS NS Record - Infoblox:

{
  "icode": "AD.201",
  "response": "record:ns/ZG5zLmJpbmRfbnMkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuLmluZm9ibG94LmxvY2FsZG9tYWlu:infoblox.localdomain/lab.itential.com/default"
}

{
  "icode": "AD.500",
  "IAPerror": {
    "origin": "Infoblox-connectorRest-handleEndResponse",
    "displayString": "Error 400 received on request",
    "recommendation": "Verify the request is accurate via debug logs and postman",
    "code": 400,
    "raw_response": {
      "status": "success",
      "code": 400,
      "response": {
        "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Cannot find the parent network for the fixed address 10.0.0.1.)",
        "code": "Client.Ibap.Data.Conflict",
        "text": "Cannot find the parent network for the fixed address 10.0.0.1."
      }
    }
  },
  "response": {
    "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Cannot find the parent network for the fixed address 10.0.0.1.)",
    "code": "Client.Ibap.Data.Conflict",
    "text": "Cannot find the parent network for the fixed address 10.0.0.1."
  }
}

Query Output

The following items show how to query successful results from the output of Create DNS NS Record - Infoblox:

Create NS Record Request Result

createdNSRecord.response

The following items show how to query failure results from the output of Create DNS NS Record - Infoblox:

Error Response Message

infobloxError.response.text

Example Inputs and Outputs

Example 1

Input:

{
  "adapterId": "Infoblox",
  "dnsView": "default",
  "nsRecord": "lab.itential.com",
  "nameServer": "infoblox.localdomain",
  "addresses": [
    {
      "address": "192.168.10.1"
    }
  ]
} 

Output:

{
  "createdNSRecord": {
    "icode": "AD.201",
    "response": "record:ns/ZG5zLmJpbmRfbnMkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuLmluZm9ibG94LmxvY2FsZG9tYWlu:infoblox.localdomain/lab.itential.com/default",
  }
} 

Example 2

Input:

{
  "adapterId": "Infoblox",
  "dnsView": "default",
  "nsRecord": "info.com",
  "nameServer": "infoblox.localdomain",
  "addresses": [
    {
      "address": "192.168.10.1"
    }
  ]
} 

Output:

{
  "createdNSRecord": null,
  "infobloxError": {
    "icode": "AD.500",
    "IAPerror": {
      "origin": "Infoblox-connectorRest-handleEndResponse",
      "displayString": "Error 400 received on request",
      "recommendation": "Verify the request is accurate via debug logs and postman",
      "code": 400,
      "raw_response": {
        "status": "success",
        "code": 400,
        "response": {
          "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
          "code": "Client.Ibap.Data.Conflict",
          "text": "The action is not allowed. A parent was not found."
        }
      }
    },
    "response": {
      "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
      "code": "Client.Ibap.Data.Conflict",
      "text": "The action is not allowed. A parent was not found."
    }
  }
} 

API Links

Create DNS PTR Record - Infoblox

A modular workflow that automates creating a DNS PTR record in Infoblox.

Capabilities include:

• The workflow is used to create a PTR record in Infoblox

Entry Point IAP Component

The primary IAP component to run Create DNS PTR Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Create DNS PTR Record - Infoblox:

hostexample

127.0.0.2

default

Infoblox

Outputs

The following table lists the outputs for Create DNS PTR Record - Infoblox:

{
  "icode": "AD.201",
  "response": "record:ptr/ZG5zLmJpbmRfcHRyJC5fZGVmYXVsdC5hcnBhLmluLWFkZHIuMTI3LjAuMC4yLmhvc3RleGFtcGxl:2.0.0.127.in-addr.arpa/default"
}

{
  "icode": "AD.500",
  "IAPerror": {
    "origin": "Infoblox-connectorRest-handleEndResponse",
    "displayString": "Error 400 received on request",
    "recommendation": "Verify the request is accurate via debug logs and postman",
    "code": 400,
    "raw_response": {
      "status": "success",
      "code": 400,
      "response": {
        "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:An invalid IP address or reverse zone was specified.)",
        "code": "Client.Ibap.Data.Conflict",
        "text": "An invalid IP address or reverse zone was specified."
      }
    }
  },
  "response": {
    "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:An invalid IP address or reverse zone was specified.)",
    "code": "Client.Ibap.Data.Conflict",
    "text": "An invalid IP address or reverse zone was specified."
  }
}

Query Output

The following items show how to query successful results from the output of Create DNS PTR Record - Infoblox:

Create PTR Record Request Result

ptrRecord.response

The following items show how to query failure results from the output of Create DNS PTR Record - Infoblox:

Error Response Message

infobloxError.response.text

Example Inputs and Outputs

Example 1

Input:

{
  "adapterId": "Infoblox",
  "hostname": "hostexample",
  "ipAddress": "127.0.0.2",
  "dnsView": "default"
} 

Output:

{
  "ptrRecord": {
    "icode": "AD.201",
    "response": "record:ptr/ZG5zLmJpbmRfcHRyJC5fZGVmYXVsdC5hcnBhLmluLWFkZHIuMTI3LjAuMC4yLmhvc3RleGFtcGxl:2.0.0.127.in-addr.arpa/default"
  }
} 

Example 2

Input:

{
  "adapterId": "Infoblox",
  "hostname": "2.5.5.5.in-addr.arpa",
  "ipAddress": "5.5.5.2",
  "dnsView": "default"
} 

Output:

{
  "ptrRecord": null,
  "infobloxError": {
    "icode": "AD.500",
    "IAPerror": {
      "origin": "Infoblox-connectorRest-handleEndResponse",
      "displayString": "Error 400 received on request",
      "recommendation": "Verify the request is accurate via debug logs and postman",
      "code": 400,
      "raw_response": {
        "status": "success",
        "code": 400,
        "response": {
          "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:An invalid IP address or reverse zone was specified.)",
          "code": "Client.Ibap.Data.Conflict",
          "text": "An invalid IP address or reverse zone was specified."
        }
      }
    },
    "response": {
      "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:An invalid IP address or reverse zone was specified.)",
      "code": "Client.Ibap.Data.Conflict",
      "text": "An invalid IP address or reverse zone was specified."
    }
  }
} 

API Links

Create Network - Infoblox

A modular workflow that automates creating a new network in Infoblox.

Capabilities include:

• The workflow is used to create a new network in Infoblox

Entry Point IAP Component

The primary IAP component to run Create Network - Infoblox is listed below:

Inputs

The following table lists the inputs for Create Network - Infoblox:

127.0.0.0/24

test create network

Infoblox

Outputs

The following table lists the outputs for Create Network - Infoblox:

{
  "icode": "AD.201",
  "response": {
    "result": "network/ZG5zLm5ldHdvcmskMTI3LjAuMC4wLzI0LzA:127.0.0.0/24/default",
    "networkIP": "127.0.0.0/24"
  }
}

{
  "icode": "AD.500",
  "IAPerror": {
    "origin": "Infoblox-connectorRest-handleEndResponse",
    "displayString": "Error 400 received on request",
    "recommendation": "Verify the request is accurate via debug logs and postman",
    "code": 400,
    "raw_response": {
      "status": "success",
      "code": 400,
      "response": {
        "Error": "AdmConProtoError: Bad value for network: '0.0.0.0'",
        "code": "Client.Ibap.Proto",
        "text": "Bad value for network: '0.0.0.0'"
      }
    }
  },
  "response": {
    "Error": "AdmConProtoError: Bad value for network: '0.0.0.0'",
    "code": "Client.Ibap.Proto",
    "text": "Bad value for network: '0.0.0.0'"
  }
}

Query Output

The following items show how to query successful results from the output of Create Network - Infoblox:

Create Network Request Result

createdNetwork.response.result

The following items show how to query failure results from the output of Create Network - Infoblox:

Error Response Message

infobloxError.response.text

Example Inputs and Outputs

Example 1

Input:

{
  "network": "127.0.0.0/24",
  "comment": "test create network",
  "adapterId": "Infoblox"
} 

Output:

{
  "createdNetwork": {
    "icode": "AD.201",
    "response": {
      "result": "network/ZG5zLm5ldHdvcmskMTI3LjAuMC4wLzI0LzA:127.0.0.0/24/default",
      "networkIP": "127.0.0.0/24"
    }
  }
} 

Example 2

Input:

{
  "network": "0.0.0.0",
  "comment": "test",
  "adapterId": "Infoblox"
} 

Output:

{
  "createdNetwork": null,
  "infobloxError": {
    "icode": "AD.500",
    "IAPerror": {
      "origin": "Infoblox-connectorRest-handleEndResponse",
      "displayString": "Error 400 received on request",
      "recommendation": "Verify the request is accurate via debug logs and postman",
      "code": 400,
      "raw_response": {
        "status": "success",
        "code": 400,
        "response": {
          "Error": "AdmConProtoError: Bad value for network: '0.0.0.0'",
          "code": "Client.Ibap.Proto",
          "text": "Bad value for network: '0.0.0.0'"
        }
      }
    },
    "response": {
      "Error": "AdmConProtoError: Bad value for network: '0.0.0.0'",
      "code": "Client.Ibap.Proto",
      "text": "Bad value for network: '0.0.0.0'"
    }
  }
} 

API Links

Create Network Container - Infoblox

A modular workflow that automates creating a new network container in Infoblox.

Capabilities include:

• The workflow is used to create a new network container in Infoblox

Entry Point IAP Component

The primary IAP component to run Create Network Container - Infoblox is listed below:

Inputs

The following table lists the inputs for Create Network Container - Infoblox:

10.0.0.0/16

Infoblox

Outputs

The following table lists the outputs for Create Network Container - Infoblox:

{
  "icode": "AD.201",
  "response": "success"
}

{
  "icode": "AD.500",
  "IAPerror": {
    "origin": "Infoblox-connectorRest-handleEndResponse",
    "displayString": "Error 400 received on request",
    "recommendation": "Verify the request is accurate via debug logs and postman",
    "code": 400,
    "raw_response": {
      "status": "success",
      "code": 400,
      "response": {
        "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Duplicate object '10.0.0.0' of type 'network_container' already exists in the database.)",
        "code": "Client.Ibap.Data.Conflict",
        "text": "Duplicate object '10.0.0.0' of type 'network_container' already exists in the database."
      }
    }
  },
  "response": {
    "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Duplicate object '10.0.0.0' of type 'network_container' already exists in the database.)",
    "code": "Client.Ibap.Data.Conflict",
    "text": "Duplicate object '10.0.0.0' of type 'network_container' already exists in the database."
  }
}

Query Output

The following items show how to query successful results from the output of Create Network Container - Infoblox:

Create Network Container Request Result

createdNetworkContainer.response

The following items show how to query failure results from the output of Create Network Container - Infoblox:

Error Response Message

infobloxError.response.text

Example Inputs and Outputs

Example 1

Input:

{
  "adapterId": "Infoblox",
  "network": "10.0.0.0/16"
} 

Output:

{
  "createdNetworkContainer": {
    "icode": "AD.201",
    "response": "success"
  }
} 

Example 2

Input:

{
  "adapterId": "Infoblox",
  "network": "10.0.0.0/8"
} 

Output:

{
  "createdNetworkContainer": null,
  "infobloxError": {
    "icode": "AD.500",
    "IAPerror": {
      "origin": "Infoblox-connectorRest-handleEndResponse",
      "displayString": "Error 400 received on request",
      "recommendation": "Verify the request is accurate via debug logs and postman",
      "code": 400,
      "raw_response": {
        "status": "success",
        "code": 400,
        "response": {
          "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Duplicate object '10.0.0.0' of type 'network_container' already exists in the database.)",
          "code": "Client.Ibap.Data.Conflict",
          "text": "Duplicate object '10.0.0.0' of type 'network_container' already exists in the database."
        }
      }
    },
    "response": {
      "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:Duplicate object '10.0.0.0' of type 'network_container' already exists in the database.)",
      "code": "Client.Ibap.Data.Conflict",
      "text": "Duplicate object '10.0.0.0' of type 'network_container' already exists in the database."
    }
  }
} 

API Links

Delete DNS A Record - Infoblox

A modular workflow that automates deleting a DNS A record in Infoblox.

Capabilities include:

• The workflow is used to delete an A record in Infoblox

Entry Point IAP Component

The primary IAP component to run Delete DNS A Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Delete DNS A Record - Infoblox:

foo.lab.itential.com

1.1.1.2

default

Infoblox

Outputs

The following table lists the outputs for Delete DNS A Record - Infoblox:

{
  "icode": "AD.200",
  "response": {
    "result": "record:a/ZG5zLmJpbmRfYSQuX2RlZmF1bHQuY29tLml0ZW50aWFsLmxhYixmb28sMS4xLjEuMg:foo.lab.itential.com/default"
  }
}

Query Output

The following items show how to query successful results from the output of Delete DNS A Record - Infoblox:

Delete A Record Request Result

deletedARecord.response.result

Example Inputs and Outputs

Example 1

Input:

{
  "hostname": "foo.lab.itential.com",
  "ipAddress": "1.1.1.2",
  "dnsView": "default",
  "adapterId": "Infoblox"
} 

Output:

{
  "deletedARecord": {
    "icode": "AD.200",
    "response": {
      "result": "record:a/ZG5zLmJpbmRfYSQuX2RlZmF1bHQuY29tLml0ZW50aWFsLmxhYixmb28sMS4xLjEuMg:foo.lab.itential.com/default"
    }
  }
} 

API Links

Delete DNS CNAME Record - Infoblox

A modular workflow that autoamtes deleting a DNS CNAME record in Infoblox.

Capabilities include:

• The workflow is used to delete a CNAME Record in Infoblox

Entry Point IAP Component

The primary IAP component to run Delete DNS CNAME Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Delete DNS CNAME Record - Infoblox:

test.demo.lab.itential.com

demo.lab.itential.com

default

Infoblox

Outputs

The following table lists the outputs for Delete DNS CNAME Record - Infoblox:

{
  "icode": "AD.200",
  "response": {
    "result": "record:cname/ZG5zLmJpbmRfY25hbWUkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuZGVtby50ZXN0:test.demo.lab.itential.com/default"
  }
}

Query Output

The following items show how to query successful results from the output of Delete DNS CNAME Record - Infoblox:

Delete CNAME Record Request Result

deletedARecord.response.result

Example Inputs and Outputs

Example 1

Input:

{
  "aliasName": "test.demo.lab.itential.com",
  "canonicalName": "demo.lab.itential.com",
  "dnsView": "default",
  "adapterId": "Infoblox"
} 

Output:

{
  "deletedCnameRecord": {
    "icode": "AD.200",
    "response": {
      "result": "record:cname/ZG5zLmJpbmRfY25hbWUkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuZGVtby50ZXN0:test.demo.lab.itential.com/default"
    }
  }
} 

API Links

Delete DNS Fixed Address Record - Infoblox

A modular workflow that automates deleting a fixed address record in Infoblox. A fixed address is a specific IP address that a DHCP server always assigns when a lease request comes from a particular MAC address of the client.

Capabilities include:

• The workflow is used to delete a Fixed Address record in Infoblox

Entry Point IAP Component

The primary IAP component to run Delete DNS Fixed Address Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Delete DNS Fixed Address Record - Infoblox:

10.0.0.2

2c:54:91:88:c9:e3

Infoblox

Outputs

The following table lists the outputs for Delete DNS Fixed Address Record - Infoblox:

{
  "icode": "AD.200",
  "response": {
    "result": "fixedaddress/ZG5zLmZpeGVkX2FkZHJlc3MkMTAuMC4wLjIuMC4u:10.0.0.2/default"
  }
}

Query Output

The following items show how to query successful results from the output of Delete DNS Fixed Address Record - Infoblox:

Delete Fixed Address Record Request Result

deletedFixedAddress.response.result

Example Inputs and Outputs

Example 1

Input:

{
  "ipAddress": "10.0.0.2",
  "macAddress": "2c:54:91:88:c9:e3",
  "adapterId": "Infoblox"
} 

Output:

{
  "deletedFixedAddress": {
    "icode": "AD.200",
    "response": {
      "result": "fixedaddress/ZG5zLmZpeGVkX2FkZHJlc3MkMTAuMC4wLjIuMC4u:10.0.0.2/default"
    }
  }
} 

API Links

Delete DNS NS Record - Infoblox

A modular workflow that automates deleting a DNS NS record in Infoblox.

Capabilities include:

• The workflow is used to delete a NS record in Infoblox

Entry Point IAP Component

The primary IAP component to run Delete DNS NS Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Delete DNS NS Record - Infoblox:

lab.itential.com

test.localdomain

default

Infoblox

Outputs

The following table lists the outputs for Delete DNS NS Record - Infoblox:

{
  "icode": "AD.200",
  "response": {
    "result": "record:ns/ZG5zLmJpbmRfbnMkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuLnRlc3QubG9jYWxkb21haW4:test.localdomain/lab.itential.com/default"
  }
}

Query Output

The following items show how to query successful results from the output of Delete DNS NS Record - Infoblox:

Delete NS Record Request Result

deletedNSRecord.response.result

Example Inputs and Outputs

Example 1

Input:

{
  "adapterId": "Infoblox",
  "dnsView": "default",
  "nsRecord": "lab.itential.com",
  "nameServer": "test.localdomain"
} 

Output:

{
  "deletedNSRecord": {
    "icode": "AD.200",
    "response": {
      "result": "record:ns/ZG5zLmJpbmRfbnMkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuLnRlc3QubG9jYWxkb21haW4:test.localdomain/lab.itential.com/default"
    }
  }
} 

API Links

Delete DNS PTR Record - Infoblox

A modular workflow that automates deleting a DNS PTR record in Infoblox.

Capabilities include:

• The workflow is used to delete a PTR record in Infoblox

Entry Point IAP Component

The primary IAP component to run Delete DNS PTR Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Delete DNS PTR Record - Infoblox:

foo

127.0.0.3

default

Infoblox

Outputs

The following table lists the outputs for Delete DNS PTR Record - Infoblox:

{
  "icode": "AD.200",
  "response": {
    "result": "record:ptr/ZG5zLmJpbmRfcHRyJC5fZGVmYXVsdC5hcnBhLmluLWFkZHIuMTI3LjAuMC4zLmZvbw:3.0.0.127.in-addr.arpa/default"
  }
}

Query Output

The following items show how to query successful results from the output of Delete DNS PTR Record - Infoblox:

Delete PTR Record Request Result

deletedPTRRecord.response.result

Example Inputs and Outputs

Example 1

Input:

{
  "adapterId": "Infoblox",
  "hostname": "foo",
  "ipAddress": "127.0.0.3",
  "dnsView": "default"
} 

Output:

{
  "deletedPTRRecord": {
    "icode": "AD.200",
    "response": {
      "result": "record:ptr/ZG5zLmJpbmRfcHRyJC5fZGVmYXVsdC5hcnBhLmluLWFkZHIuMTI3LjAuMC4zLmZvbw:3.0.0.127.in-addr.arpa/default"
    }
  }
} 

API Links

Delete Network - Infoblox

A modular workflow that automates deleting a network in Infoblox.

Capabilities include:

• The workflow is used to delete a network in Infoblox

Entry Point IAP Component

The primary IAP component to run Delete Network - Infoblox is listed below:

Inputs

The following table lists the inputs for Delete Network - Infoblox:

127.0.0.0/24

Infoblox

Outputs

The following table lists the outputs for Delete Network - Infoblox:

{
  "icode": "AD.200",
  "response": "success"
}

{
  "icode": "AD.999",
  "IAPerror": {
    "origin": "Infoblox-adapter-deleteNetworkv2",
    "displayString": "Network not found",
    "recommendation": "Make sure the network exists"
  }
}

Query Output

The following items show how to query successful results from the output of Delete Network - Infoblox:

Delete Network Request Result

deletedNetwork.response

The following items show how to query failure results from the output of Delete Network - Infoblox:

Error Response Message

infobloxError.IAPerror.displayString

Example Inputs and Outputs

Example 1

Input:

{
  "networkIP": "127.0.0.0/24",
  "adapterId": "Infoblox"
} 

Output:

{
  "deletedNetwork": {
    "icode": "AD.200",
    "response": "success"
  }
} 

Example 2

Input:

{
  "networkIP": "1.1.1.1",
  "adapterId": "Infoblox"
} 

Output:

{
  "deletedNetwork": null,
  "infobloxError": {
    "icode": "AD.999",
    "IAPerror": {
      "origin": "Infoblox-adapter-deleteNetworkv2",
      "displayString": "Network not found",
      "recommendation": "Make sure the network exists"
    }
  }
} 

API Links

Delete Network Container - Infoblox

A modular workflow that automates deleting a network container in Infoblox.

Capabilities include:

• The workflow is used to delete a network container in Infoblox

Entry Point IAP Component

The primary IAP component to run Delete Network Container - Infoblox is listed below:

Inputs

The following table lists the inputs for Delete Network Container - Infoblox:

10.0.0.0/16

Infoblox

Outputs

The following table lists the outputs for Delete Network Container - Infoblox:

{
  "icode": "AD.200",
  "response": "networkcontainer/ZG5zLm5ldHdvcmtfY29udGFpbmVyJDEwLjAuMC4wLzE2LzA:10.0.0.0/16/default"
}

Query Output

The following items show how to query successful results from the output of Delete Network Container - Infoblox:

Delete Network Container Request Result

deletedNetworkContainers.response

Example Inputs and Outputs

Example 1

Input:

{
  "networkIP": "10.0.0.0/16",
  "adapterId": "Infoblox"
} 

Output:

{
  "deletedNetworkContainer": {
    "icode": "AD.200",
    "response": "networkcontainer/ZG5zLm5ldHdvcmtfY29udGFpbmVyJDEwLjAuMC4wLzE2LzA:10.0.0.0/16/default"
  }
} 

API Links

Modify DNS A Record - Infoblox

A modular workflow that automates modifying a DNS A record in Infoblox.

Capabilities include:

• The workflow is used to modify A record in Infoblox

Entry Point IAP Component

The primary IAP component to run Modify DNS A Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Modify DNS A Record - Infoblox:

test.lab.itential.com

1.1.1.1

foo.lab.itential.com

1.1.1.2

default

Infoblox

Outputs

The following table lists the outputs for Modify DNS A Record - Infoblox:

{
  "icode": "AD.200",
  "response": {
    "result": "record:a/ZG5zLmJpbmRfYSQuX2RlZmF1bHQuY29tLml0ZW50aWFsLmxhYixmb28sMS4xLjEuMg:foo.lab.itential.com/default"
  }
}

{
  "icode": "AD.500",
  "IAPerror": {
    "origin": "Infoblox-connectorRest-handleEndResponse",
    "displayString": "Error 400 received on request",
    "recommendation": "Verify the request is accurate via debug logs and postman",
    "code": 400,
    "raw_response": {
      "status": "success",
      "code": 400,
      "response": {
        "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
        "code": "Client.Ibap.Data.Conflict",
        "text": "The action is not allowed. A parent was not found."
      }
    }
  },
  "response": {
    "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
    "code": "Client.Ibap.Data.Conflict",
    "text": "The action is not allowed. A parent was not found."
  }
}

Query Output

The following items show how to query successful results from the output of Modify DNS A Record - Infoblox:

Update A Record Request Result

updatedARecord.response.result

The following items show how to query failure results from the output of Modify DNS A Record - Infoblox:

Error Response Message

infobloxError.response.text

Example Inputs and Outputs

Example 1

Input:

{
  "currentHostname": "test.lab.itential.com",
  "currentIpAddress": "1.1.1.1",
  "dnsView": "default",
  "adapterId": "Infoblox",
  "updatedHostname": "foo.lab.itential.com",
  "updatedIpAddress": "1.1.1.2"
} 

Output:

{
  "updatedARecord": {
    "icode": "AD.200",
    "response": {
      "result": "record:a/ZG5zLmJpbmRfYSQuX2RlZmF1bHQuY29tLml0ZW50aWFsLmxhYixmb28sMS4xLjEuMg:foo.lab.itential.com/default"
    }
  }
} 

Example 2

Input:

{
  "currentHostname": "test.lab.itential.com",
  "currentIpAddress": "1.1.1.1",
  "dnsView": "default",
  "adapterId": "Infoblox",
  "updatedHostname": "test.info",
  "updatedIpAddress": "1.1.1.2"
} 

Output:

{
  "infobloxError": {
    "icode": "AD.500",
    "IAPerror": {
      "origin": "Infoblox-connectorRest-handleEndResponse",
      "displayString": "Error 400 received on request",
      "recommendation": "Verify the request is accurate via debug logs and postman",
      "code": 400,
      "raw_response": {
        "status": "success",
        "code": 400,
        "response": {
          "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
          "code": "Client.Ibap.Data.Conflict",
          "text": "The action is not allowed. A parent was not found."
        }
      }
    },
    "response": {
      "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
      "code": "Client.Ibap.Data.Conflict",
      "text": "The action is not allowed. A parent was not found."
    }
  },
  "updatedARecord": null
} 

API Links

Modify DNS CNAME Record - Infoblox

A modular workflow that automates modifying a DNS CNAME record in Infoblox.

Capabilities include:

• The workflow is used to modify CNAME record in Infoblox

Entry Point IAP Component

The primary IAP component to run Modify DNS CNAME Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Modify DNS CNAME Record - Infoblox:

cnametest.demo.lab.itential.com

demo.lab.itential.com

default

test.demo.lab.itential.com

demo.lab.itential.com

Infoblox

Outputs

The following table lists the outputs for Modify DNS CNAME Record - Infoblox:

{
  "icode": "AD.200",
  "response": {
    "result": "record:cname/ZG5zLmJpbmRfY25hbWUkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuZGVtby50ZXN0:test.demo.lab.itential.com/default"
  }
}

{
  "icode": "AD.500",
  "IAPerror": {
    "origin": "Infoblox-connectorRest-handleEndResponse",
    "displayString": "Error 400 received on request",
    "recommendation": "Verify the request is accurate via debug logs and postman",
    "code": 400,
    "raw_response": {
      "status": "success",
      "code": 400,
      "response": {
        "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
        "code": "Client.Ibap.Data.Conflict",
        "text": "The action is not allowed. A parent was not found."
      }
    }
  },
  "response": {
    "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
    "code": "Client.Ibap.Data.Conflict",
    "text": "The action is not allowed. A parent was not found."
  }
}

Query Output

The following items show how to query successful results from the output of Modify DNS CNAME Record - Infoblox:

Update CNAME Record Request Result

updatedCnameRecord.response.result

The following items show how to query failure results from the output of Modify DNS CNAME Record - Infoblox:

Error Response Message

infobloxError.response.text

Example Inputs and Outputs

Example 1

Input:

{
  "currentAliasName": "cnametest.demo.lab.itential.com",
  "currentCanonicalName": "demo.lab.itential.com",
  "dnsView": "default",
  "adapterId": "Infoblox",
  "newAliasName": "test.demo.lab.itential.com",
  "newCanonicalName": "demo.lab.itential.com"
} 

Output:

{
  "updatedCnameRecord": {
    "icode": "AD.200",
    "response": {
      "result": "record:cname/ZG5zLmJpbmRfY25hbWUkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuZGVtby50ZXN0:test.demo.lab.itential.com/default"
    }
  }
} 

Example 2

Input:

{
  "currentAliasName": "cnametest.demo.lab.itential.com",
  "currentCanonicalName": "demo.lab.itential.com",
  "dnsView": "default",
  "adapterId": "Infoblox",
  "newAliasName": "cnametest.demo.info.com",
  "newCanonicalName": "demo.info.com"
} 

Output:

{
  "infobloxError": {
    "icode": "AD.500",
    "IAPerror": {
      "origin": "Infoblox-connectorRest-handleEndResponse",
      "displayString": "Error 400 received on request",
      "recommendation": "Verify the request is accurate via debug logs and postman",
      "code": 400,
      "raw_response": {
        "status": "success",
        "code": 400,
        "response": {
          "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
          "code": "Client.Ibap.Data.Conflict",
          "text": "The action is not allowed. A parent was not found."
        }
      }
    },
    "response": {
      "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)",
      "code": "Client.Ibap.Data.Conflict",
      "text": "The action is not allowed. A parent was not found."
    }
  },
  "updatedCnameRecord": null
} 

API Links

Modify DNS Fixed Address Record - Infoblox

A modular workflow that automates modifying a fixed address record in Infoblox. A fixed address is a specific IP address that a DHCP server always assigns when a lease request comes from a particular MAC address of the client.

Capabilities include:

• The workflow is used to modify Fixed Address record in Infoblox

Entry Point IAP Component

The primary IAP component to run Modify DNS Fixed Address Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Modify DNS Fixed Address Record - Infoblox:

10.0.0.1

aa:bb:cc:45:67:45

10.0.0.2

2c:54:91:88:c9:e3

Infoblox

Outputs

The following table lists the outputs for Modify DNS Fixed Address Record - Infoblox:

{
  "icode": "AD.200",
  "response": {
    "result": "fixedaddress/ZG5zLmZpeGVkX2FkZHJlc3MkMTAuMC4wLjIuMC4u:10.0.0.2/default"
  }
}

{
  "icode": "AD.500",
  "IAPerror": {
    "origin": "Infoblox-connectorRest-handleEndResponse",
    "displayString": "Error 400 received on request",
    "recommendation": "Verify the request is accurate via debug logs and postman",
    "code": 400,
    "raw_response": {
      "status": "success",
      "code": 400,
      "response": {
        "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The IP address 1.1.1.1 is not valid for the network 10.0.0.0/24.)",
        "code": "Client.Ibap.Data.Conflict",
        "text": "The IP address 1.1.1.1 is not valid for the network 10.0.0.0/24."
      }
    }
  },
  "response": {
    "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The IP address 1.1.1.1 is not valid for the network 10.0.0.0/24.)",
    "code": "Client.Ibap.Data.Conflict",
    "text": "The IP address 1.1.1.1 is not valid for the network 10.0.0.0/24."
  }
}

Query Output

The following items show how to query successful results from the output of Modify DNS Fixed Address Record - Infoblox:

Update Fixed Address Record Request Result

updatedFixedAddress.response.result

The following items show how to query failure results from the output of Modify DNS Fixed Address Record - Infoblox:

Error Response Message

infobloxError.response.text

Example Inputs and Outputs

Example 1

Input:

{
  "currentIpAddress": "10.0.0.1",
  "currentMacAddress": "aa:bb:cc:45:67:45",
  "adapterId": "Infoblox",
  "newIpAddress": "10.0.0.2",
  "newMacAddress": "2c:54:91:88:c9:e3"
} 

Output:

{
  "updatedFixedAddress": {
    "icode": "AD.200",
    "response": {
      "result": "fixedaddress/ZG5zLmZpeGVkX2FkZHJlc3MkMTAuMC4wLjIuMC4u:10.0.0.2/default"
    }
  }
} 

Example 2

Input:

{
  "currentIpAddress": "10.0.0.1",
  "currentMacAddress": "aa:bb:cc:45:67:45",
  "adapterId": "Infoblox",
  "newIpAddress": "1.1.1.1",
  "newMacAddress": "2c:54:91:88:c9:e3"
} 

Output:

{
  "infobloxError": {
    "icode": "AD.500",
    "IAPerror": {
      "origin": "Infoblox-connectorRest-handleEndResponse",
      "displayString": "Error 400 received on request",
      "recommendation": "Verify the request is accurate via debug logs and postman",
      "code": 400,
      "raw_response": {
        "status": "success",
        "code": 400,
        "response": {
          "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The IP address 1.1.1.1 is not valid for the network 10.0.0.0/24.)",
          "code": "Client.Ibap.Data.Conflict",
          "text": "The IP address 1.1.1.1 is not valid for the network 10.0.0.0/24."
        }
      }
    },
    "response": {
      "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The IP address 1.1.1.1 is not valid for the network 10.0.0.0/24.)",
      "code": "Client.Ibap.Data.Conflict",
      "text": "The IP address 1.1.1.1 is not valid for the network 10.0.0.0/24."
    }
  },
  "updatedFixedAddress": null
} 

API Links

Modify DNS NS Record - Infoblox

A modular workflow that automates modifying a DNS NS record in Infoblox.

Capabilities include:

• The workflow is used to modify NS record in Infoblox

Entry Point IAP Component

The primary IAP component to run Modify DNS NS Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Modify DNS NS Record - Infoblox:

lab.itential.com

infoblox.localdomain

test.localdomain

default

Infoblox

Outputs

The following table lists the outputs for Modify DNS NS Record - Infoblox:

{
  "icode": "AD.200",
  "response": {
    "result": "record:ns/ZG5zLmJpbmRfbnMkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuLnRlc3QubG9jYWxkb21haW4:test.localdomain/lab.itential.com/default"
  }
}

Query Output

The following items show how to query successful results from the output of Modify DNS NS Record - Infoblox:

Update NS Record Request Result

updatedNSRecord.response.result

Example Inputs and Outputs

Example 1

Input:

{
  "adapterId": "Infoblox",
  "dnsView": "default",
  "currentNsRecord": "lab.itential.com",
  "currentNameServer": "infoblox.localdomain",
  "newNameServer": "test.localdomain"
} 

Output:

{
  "updatedNSRecord": {
    "icode": "AD.200",
    "response": {
      "result": "record:ns/ZG5zLmJpbmRfbnMkLl9kZWZhdWx0LmNvbS5pdGVudGlhbC5sYWIuLnRlc3QubG9jYWxkb21haW4:test.localdomain/lab.itential.com/default"
    }
  }
} 

API Links

Modify DNS PTR Record - Infoblox

A modular workflow that automates modifying a DNS PTR record in Infoblox.

Capabilities include:

• The workflow is used to modify PTR record in Infoblox

Entry Point IAP Component

The primary IAP component to run Modify DNS PTR Record - Infoblox is listed below:

Inputs

The following table lists the inputs for Modify DNS PTR Record - Infoblox:

127.0.0.2

hostexample

127.0.0.3

foo

default

Infoblox

Outputs

The following table lists the outputs for Modify DNS PTR Record - Infoblox:

{
  "icode": "AD.200",
  "response": {
    "result": "record:ptr/ZG5zLmJpbmRfcHRyJC5fZGVmYXVsdC5hcnBhLmluLWFkZHIuMTI3LjAuMC4zLmZvbw:3.0.0.127.in-addr.arpa/default"
  }
}

{
  "icode": "AD.500",
  "IAPerror": {
    "origin": "Infoblox-connectorRest-handleEndResponse",
    "displayString": "Error 400 received on request",
    "recommendation": "Verify the request is accurate via debug logs and postman",
    "code": 400,
    "raw_response": {
      "status": "success",
      "code": 400,
      "response": {
        "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:An invalid IP address or reverse zone was specified.)",
        "code": "Client.Ibap.Data.Conflict",
        "text": "An invalid IP address or reverse zone was specified."
      }
    }
  },
  "response": {
    "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:An invalid IP address or reverse zone was specified.)",
    "code": "Client.Ibap.Data.Conflict",
    "text": "An invalid IP address or reverse zone was specified."
  }
}

Query Output

The following items show how to query successful results from the output of Modify DNS PTR Record - Infoblox:

Update PTR Record Request Result

updatedPTRRecord.response.result

The following items show how to query failure results from the output of Modify DNS PTR Record - Infoblox:

Error Response Message

infobloxError.response.text

Example Inputs and Outputs

Example 1

Input:

{
  "currentIpAddress": "127.0.0.2",
  "currentHostname": "hostexample",
  "dnsView": "default",
  "adapterId": "Infoblox",
  "newIpAddress": "127.0.0.3",
  "newHostname": "foo"
} 

Output:

{
  "updatedPTRRecord": {
    "icode": "AD.200",
    "response": {
      "result": "record:ptr/ZG5zLmJpbmRfcHRyJC5fZGVmYXVsdC5hcnBhLmluLWFkZHIuMTI3LjAuMC4zLmZvbw:3.0.0.127.in-addr.arpa/default"
    }
  }
} 

Example 2

Input:

{
  "currentIpAddress": "127.0.0.3",
  "currentHostname": "foo",
  "dnsView": "default",
  "adapterId": "Infoblox",
  "newIpAddress": "5.5.5.5",
  "newHostname": "bar"
} 

Output:

{
  "infobloxError": {
    "icode": "AD.500",
    "IAPerror": {
      "origin": "Infoblox-connectorRest-handleEndResponse",
      "displayString": "Error 400 received on request",
      "recommendation": "Verify the request is accurate via debug logs and postman",
      "code": 400,
      "raw_response": {
        "status": "success",
        "code": 400,
        "response": {
          "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:An invalid IP address or reverse zone was specified.)",
          "code": "Client.Ibap.Data.Conflict",
          "text": "An invalid IP address or reverse zone was specified."
        }
      }
    },
    "response": {
      "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:An invalid IP address or reverse zone was specified.)",
      "code": "Client.Ibap.Data.Conflict",
      "text": "An invalid IP address or reverse zone was specified."
    }
  },
  "updatedPTRRecord": null
} 

API Links

Additional Information

Support

Please use your Itential Customer Success account if you need support when using this Workflow Project.