Update DNS Record operation

The Update DNS Record operation enables you to edit and update any type of DNS records in the Infoblox application.

The Update DNS Record operation runs a query based on the elements that you specify. If multiple records match the query, the adapter updates all the records. This enables you to update multiple records of the same type simultaneously.

Adapter request elements for updating a DNS record of type A

Element

Description

Required

<operation-name>

Specifies the name of the operation: update-dns-record

Yes

<target>

Contains the following elements:

  • <host>
  • <user-name>
  • <password>
  • <timeout-secs>

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<host>

Specifies the host name (fully qualified domain name) or IP address of the Infoblox Grid Manager

Valid value: Any string

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<user-name>

Specifies the user name required to connect to the Infoblox Grid Manager

Valid value: Any string

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<password>

Specifies the password that corresponds to <user-name>

The <password> element can contain an encryption-type attribute (the Encryption Type field on the form in the form view) that specifies whether the password is encrypted.

Valid value for <password>: Any string

Valid values for encryption-type: base64, plain (default)

Conditional:

  • Required if not specified in the request
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<timeout-secs>

Specifies the time, in seconds, after which the request expires

Valid values: Any integer

Default value: 60 seconds

No

<parameters>

Contains the elements required to execute the operation

Yes

<record-type>

Specifies the type of DNS record that you want to create

Valid value: A

Yes

<query>

Specifies the parent tag for querying DNS records

Yes

<a-name>

Specifies the name of the A type of a DNS record in a fully qualified domain name (FQDN) format

The adapter queries for all the records that match the specified name.

Yes

<ip-address>

Specifies the IP address associated with the A record to uniquely identify the record

No

<dns-view>

Specifies the DNS view in which the A record exists

If you do not specify the DNS view, the adapter searches for the record in all views in the application

No

<update>

Specifies the parent element for updating DNS Record fields

Yes

<a-name>

Specifies the name of the A type of a DNS record in a fully qualified domain name (FQDN) format

No

<ip-address>

Specifies the IPv4 address associated with the A record

No

<dns-view>

Specifies the DNS view in which the record is updated

No

<comment>

Specifies a user comment

No

<disable>

Specifies whether to disable the DNS record after it is updated

Valid values: true, false (default)

No

<ttl>

Specifies, in seconds, the time required to start and run the DNS record

Default value: 120 seconds

No

<scheduled-at>

Specifies the date and time, in ISO 8601 extended format, at which you want to execute the operation

Example: 2008-10-21T10:56:00Z

No

<extensible-attributes>

Contains the <attribute> element

No

<attribute>

Contains a key-value pair designated by the <key> and <value> elements that contain location-specific information for the host, such as building, site, and so on

You can specify multiple <attribute> elements.

Example:

<extensible-attributes>
<attribute>
<key>Building</key>
<value>Building 101</value>
</attribute>
<attribute>
<key>Floor</key>
<value>4</value>
</attribute>
</extensible-attributes>

No



 Sample

<items>
    <item>
        <target>
            <host>localhost</host>
            <user-name>admin</user-name>
            <password encryption-type="Base64">YWRtaW4=</password>
            <timeout-secs>120</timeout-secs>
        </target>
            <parameters>
            <record-type>A</record-type>
                    <query>
                            <a-name>admin.demo.com</a-name>
                            <ip-address>10.0.0.0</ip-address>
                            <dns-view>default</dns-view>
                    </query>
                    <update>
                            <a-name>admin.demo.com</a-name>
                            <ip-address>10.0.0.0</ip-address>
                            <dns-view>default</dns-view>
                            <comment>updated comment</comment>
                            <disable>true</disable>
                            <ttl>120</ttl>
                            <scheduled-at>2012-11-29T18:30:19+05:30</scheduled-at>
                            <extensible-attributes>
                            <attribute>
                                <key>Site</key>
                                <value>sample site</value>
                            </attribute>
                        </extensible-attributes>
                    </update>
           </parameters>
        </item>
</items>


 Sample adapter response for updating a DNS Record of type A

<infoblox-vnios-response>
  <metadata>
    <response-count>1</response-count>
    <status>success</status>
  </metadata>
  <responses>
    <update-dns-record-response>
      <metadata>
        <os-id>Windows 2003</os-id>
        <os-version>5.2</os-version>
        <os-arch>x86</os-arch>
        <status>success</status>
        <target>10.128.36.17</target>
      </metadata>
      <commands-output>
        <command-output>
          <metadata>
            <command>perl "C:\BMC Software\AO\Server\7_6_02_01\CDP\server\grids\GRID1\library\adapters\implementations\bmc-adapter-infoblox-nios-actor_20.13.01.00_16\update_dns_record.pl"  "10.128.36.17" "admin" "infoblox" "record-type:A" "query-a-name:admin.demo.com" "query-ip-address:10.0.0.43" "query-dns-view:default" "update-a-name:admin.demo.com" "update-ip-address:10.0.0.55" "update-dns-view:default" "update-comment:updated comment by adapter" "update-disable:true" "update-ttl:240" "update-extensible-attributes:{'Site'=&gt;'Mumbai',},"</command>
            <line-count>2</line-count>
            <execution-milliseconds>13344</execution-milliseconds>
            <exit-code>0</exit-code>
            <status>success</status>
          </metadata>
          <output>
            <line index="1">Response Code:0</line>
            <line index="2">Response Description:Operation succeeded</line>
          </output>
        </command-output>
      </commands-output>
    </update-dns-record-response>
  </responses>
</infoblox-vnios-response>


Back to top

Adapter request elements for updating a DNS record of type PTR

Element

Description

Required

<operation-name>

Specifies the name of the operation: update-dns-record

Yes

<target>

Contains the following elements:

  • <host>
  • <user-name>
  • <password>
  • <timeout-secs>

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<host>

Specifies the host name (fully qualified domain name) or IP address of the Infoblox Grid Manager

Valid value: Any string

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<user-name>

Specifies the user name required to connect to the Infoblox Grid Manager

Valid value: Any string

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<password>

Specifies the password that corresponds to <user-name>

The <password> element can contain an encryption-type attribute (the Encryption Type field on the form in the form view) that specifies whether the password is encrypted.

Valid value for <password>: Any string

Valid values for encryption-type: base64, plain (default)

Conditional:

  • Required if not specified in the request
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<timeout-secs>

Specifies the time, in seconds, after which the request expires

Valid values: Any integer

Default value: 60 seconds

No

<parameters>

Contains the elements required to execute the operation

Yes

<record-type>

Specifies the type of DNS record that you want to create

Valid value: PTR

Yes

<query>

Specifies the parent tag for querying DNS records

No

<ptrd-name>

Specifies the domain name of the PTR record

Yes

<ptr-name>

Specifies the host name to which the PTR record points 

You must specify the PTR name in a fully qualified domain name format (FQDN) else the record is not updated and you receive the following error message in the adapter response:

Response Description:Internal error

No

<dns-view>

Specifies the DNS view in which the PTR record exists

If you do not specify the DNS view, the adapter searches for the record in all views in the application

No

<update>

Specifies the parent element for updating DNS record fields

No

<ipv4-address>

Specifies the IPv4 address associated with the PTR record

If you want to update the domain name of the PTR record, use the <ipv4-address> element.

No

<ipv6-address>

Specifies the IPv6 address associated with the PTR record

If you want to update the domain name of the PTR record, use the <ipv6-address> element.

No

<dns-view>

Specifies the DNS view in which the record is updated

No

<comment>

Specifies a user comment

No

<disable>

Specifies whether to disable the DNS record after it is updated

Valid values: true, false (default)

No

<ttl>

Specifies, in seconds, the time required to start and run the DNS record

Default value: 120 seconds

No

<scheduled-at>

Specifies the date and time, in ISO 8601 extended format, at which you want to execute the operation

Example: 2008-10-21T10:56:00Z

No

<extensible-attributes>

Contains the <attribute> element

No

<attribute>

Contains a key-value pair designated by the <key> and <value> elements that contain location-specific information for the host, such as building, site, and so on

You can specify multiple <attribute> elements.

Example:

<extensible-attributes>
<attribute>
<key>Building</key>
<value>Building 101</value>
</attribute>
<attribute>
<key>Floor</key>
<value>4</value>
</attribute>
</extensible-attributes>

No



 Sample

<items>
    <item>
        <target>
            <host>localhost</host>
            <user-name>admin</user-name>
            <password encryption-type="Base64">YWRtaW4=</password>
            <timeout-secs>120</timeout-secs>
        </target>
            <parameters>
            <record-type>PTR</record-type>
                    <query>
                            <ptrd-name>host.demo.com</ptrd-name>
                            <ptr-name>PTRNAME</ptr-name>
                            <dns-view>default</dns-view>
                    </query>
                    <update>
                            <ptr-name>host.demo.com</ptr-name>
                            <ipv4-address>10.0.0.89</ipv4-address>
                            <ipv6-address>0:0:0:0:0</ipv6-address>
                            <dns-view>default</dns-view>
                            <comment>updated comment</comment>
                            <disable>true</disable>
                            <ttl>120</ttl>
                            <scheduled-at>2012-11-29T18:30:19+05:30</scheduled-at>
                            <extensible-attributes>
                            <attribute>
                                <key>Site</key>
                                <value>sample site</value>
                            </attribute>
                        </extensible-attributes>
                    </update>
           </parameters>
        </item>
</items>


 Sample adapter response for updating a DNS Record of type PTR

<infoblox-vnios-response>
  <metadata>
    <response-count>1</response-count>
    <status>success</status>
  </metadata>
  <responses>
    <update-dns-record-response>
      <metadata>
        <os-id>Windows 2003</os-id>
        <os-version>5.2</os-version>
        <os-arch>x86</os-arch>
        <status>success</status>
        <target>10.128.36.17</target>
      </metadata>
      <commands-output>
        <command-output>
          <metadata>
            <command>perl "C:\BMC Software\AO\Server\7_6_02_01\CDP\server\grids\GRID1\library\adapters\implementations\bmc-adapter-infoblox-nios-actor_20.13.01.00_16\update_dns_record.pl"  "10.128.36.17" "admin" "infoblox" "record-type:PTR" "query-ptrd-name:36.0.0.10.in-addr.arpa" "query-ptr-name:UPDATEDPTRNAME" "query-dns-view:default" "update-ptr-name:updatedname" "update-ipv4-address:10.0.0.26" "update-dns-view:default" "update-comment:updated comment" "update-disable:true" "update-ttl:120" "update-extensible-attributes:{'Site'=&gt;'sample site',},"</command>
            <line-count>2</line-count>
            <execution-milliseconds>47156</execution-milliseconds>
            <exit-code>0</exit-code>
            <status>success</status>
          </metadata>
          <output>
            <line index="1">Response Code:0</line>
            <line index="2">Response Description:Operation succeeded</line>
          </output>
        </command-output>
      </commands-output>
    </update-dns-record-response>
  </responses>
</infoblox-vnios-response>


Back to top

Adapter request elements for updating a DNS record of type CNAME

Element

Description

Required

<operation-name>

Specifies the name of the operation: update-dns-record

Yes

<target>

Contains the following elements:

  • <host>
  • <user-name>
  • <password>
  • <timeout-secs>

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<host>

Specifies the host name (fully qualified domain name) or IP address of the Infoblox Grid Manager

Valid value: Any string

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<user-name>

Specifies the user name required to connect to the Infoblox Grid Manager

Valid value: Any string

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<password>

Specifies the password that corresponds to <user-name>

The <password> element can contain an encryption-type attribute (the Encryption Type field on the form in the form view) that specifies whether the password is encrypted.

Valid value for <password>: Any string

Valid values for encryption-type: base64, plain (default)

Conditional:

  • Required if not specified in the request
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<timeout-secs>

Specifies the time, in seconds, after which the request expires

Valid values: Any integer

Default value: 60 seconds

No

<parameters>

Contains the elements required to execute the operation

Yes

<record-type>

Specifies the type of DNS record that you want to create

Valid value: CNAME

Yes

<query>

Specifies the parent tag for querying DNS records

No

<cname-name>

Specifies the alias for a CNAME type of DNS record in an FQDN format

Yes

<dns-view>

Specifies the DNS view in which the CNAME record exists

If you do not specify the DNS view, the adapter searches for the record in all views in the application

No

<update>

Specifies the parent element for updating DNS record fields

No

<cname-name>

Specifies the host name in the FQDN format, that is, host name followed by the domain name

Example:1.0.0.10.in-addr.arpa

Yes

<canonical-name>

Specifies the complete canonical or official host nameo of a CNAME record

Yes

<dns-view>

Specifies the DNS view in which the record is updated

No

<comment>

Specifies a user comment

No

<disable>

Specifies whether to disable the DNS record after it is updated

Valid values: true, false (default)

No

<ttl>

Specifies, in seconds, the time required to start and run the DNS record

Default value: 120 seconds

No

<scheduled-at>

Specifies the date and time, in ISO 8601 extended format, at which you want to execute the operation

Example: 2008-10-21T10:56:00Z

No

<extensible-attributes>

Contains the <attribute> element

No

<attribute>

Contains a key-value pair designated by the <key> and <value> elements that contain location-specific information for the host, such as building, site, and so on

You can specify multiple <attribute> elements.

Example:

<extensible-attributes>
<attribute>
<key>Building</key>
<value>Building 101</value>
</attribute>
<attribute>
<key>Floor</key>
<value>4</value>
</attribute>
</extensible-attributes>

No



 Sample

<items>
    <item>
        <target>
            <host>localhost</host>
            <user-name>admin</user-name>
            <password encryption-type="Base64">YWRtaW4=</password>
            <timeout-secs>120</timeout-secs>
        </target>
            <parameters>
            <record-type>CNAME</record-type>
                    <query>
                            <cname-name>1.0.0.10.in-addr.arpa</cname-name>
                            <dns-view>default</dns-view>
                    </query>
                    <update>
                            <cname-name>1.0.0.10.in-addr.arpa</cname-name>
                            <canonical-name>1.0.0.10.in-addr.arpa</canonical-name>
                            <dns-view>default</dns-view>
                            <comment>updated comment</comment>
                            <disable>true</disable>
                            <ttl>120</ttl>
                            <scheduled-at>2012-11-29T18:30:19+05:30</scheduled-at>
                            <extensible-attributes>
                            <attribute>
                                <key>Site</key>
                                <value>sample site</value>
                            </attribute>
                        </extensible-attributes>
                    </update>
           </parameters>
        </item>
</items>


 Sample adapter response for updating a DNS record of type CNAME

<infoblox-vnios-response>
  <metadata>
    <response-count>1</response-count>
    <status>success</status>
  </metadata>
  <responses>
    <update-dns-record-response>
      <metadata>
        <os-id>Windows 2003</os-id>
        <os-version>5.2</os-version>
        <os-arch>x86</os-arch>
        <status>success</status>
        <target>10.128.36.17</target>
      </metadata>
      <commands-output>
        <command-output>
          <metadata>
            <command>perl "C:\BMC Software\AO\Server\7_6_02_01\CDP\server\grids\GRID1\library\adapters\implementations\bmc-adapter-infoblox-nios-actor_20.13.01.00_16\update_dns_record.pl"  "10.128.36.17" "admin" "infoblox" "record-type:CNAME" "query-cname-name:73.0.0.10.in-addr.arpa" "query-dns-view:default" "update-cname-name:72.0.0.10.in-addr.arpa" "update-canonical-name:Updated CanonicalName" "update-dns-view:default" "update-comment:updated comment" "update-disable:true" "update-ttl:120" "update-extensible-attributes:{'Site'=&gt;'sample site',},"</command>
            <line-count>2</line-count>
            <execution-milliseconds>9641</execution-milliseconds>
            <exit-code>0</exit-code>
            <status>success</status>
          </metadata>
          <output>
            <line index="1">Response Code:0</line>
            <line index="2">Response Description:Operation succeeded</line>
          </output>
        </command-output>
      </commands-output>
    </update-dns-record-response>
  </responses>
</infoblox-vnios-response>


Back to top

Adapter request elements for updating a DNS record of type SRV

Element

Description

Required

<operation-name>

Specifies the name of the operation: update-dns-record

Yes

<target>

Contains the following elements:

  • <host>
  • <user-name>
  • <password>
  • <timeout-secs>

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<host>

Specifies the host name (fully qualified domain name) or IP address of the Infoblox Grid Manager

Valid value: Any string

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<user-name>

Specifies the user name required to connect to the Infoblox Grid Manager

Valid value: Any string

Conditional:

  • Required if not specified in the configuration
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<password>

Specifies the password that corresponds to <user-name>

The <password> element can contain an encryption-type attribute (the Encryption Type field on the form in the form view) that specifies whether the password is encrypted.

Valid value for <password>: Any string

Valid values for encryption-type: base64, plain (default)

Conditional:

  • Required if not specified in the request
  • If specified in the configuration and request, the value in the request overrides the value in the configuration

<timeout-secs>

Specifies the time, in seconds, after which the request expires

Valid values: Any integer

Default value: 60 seconds

No

<parameters>

Contains the elements required to execute the operation

Yes

<record-type>

Specifies the type of DNS record that you want to create

Valid value: SRV

Yes

<query>

Specifies the parent tag for querying DNS records

No

<srv-name>

Specifies the host name in the FQDN format, that is, host name followed by the authoritative forward-mapping zone name

Example: admin.demo.com

Yes

<srv-port>

Specifies the port number for the SRV record

Yes

<srv-priority>

Specifies the priority for the SRV record

The priority determines the order in which the client attempts to contact the target host.

Valid values: Any integer between 0 to 65535

Yes

<srv-weight>

Specifies the weight of the SRV record 

Valid values: Any integer between 0 to 65535

Yes

<srv-target>

Specifies the canonical domain name for the host with the name of the authoritative forward-mapping zone

Example: admin.demo.com

Here demo.com is the name of the authoritative forward-mapping zone.

No

<dns-view>

Specifies the DNS view in which the SRV record exists

If you do not specify the DNS view, the adapter searches for the record in all views in the application

No

<update>

Specifies the parent element for updating DNS record fields

No

<srv-name>

Specifies the host name that you want to update, in an FQDN format

Yes

<srv-port>

Specifies the port number for the SRV record

Yes

<srv-priority>

Specifies the priority for the SRV record

Valid values: Any integer between 0 to 65535

Yes

<srv-weight>

Specifies the weight of the SRV record

Valid values: Any integer between 0 to 65535

Yes

<srv-target>

Specifies the canonical domain name for the host with the name of the authoritative forward-mapping zone

No

<dns-view>

Specifies the DNS view in which the record is updated

No

<comment>

Specifies a user comment

No

<disable>

Specifies whether to disable the DNS record after it is updated

Valid values: true, false (default)

No

<ttl>

Specifies, in seconds, the time required to start and run the DNS record

Default value: 120 seconds

No

<scheduled-at>

Specifies the date and time, in ISO 8601 extended format, at which you want to execute the operation

Example: 2008-10-21T10:56:00Z

No

<extensible-attributes>

Contains the <attribute> element

No

<attribute>

Contains a key-value pair designated by the <key> and <value> elements that contain location-specific information for the host, such as building, site, and so on

You can specify multiple <attribute> elements.

Example:

<extensible-attributes>
<attribute>
<key>Building</key>
<value>Building 101</value>
</attribute>
<attribute>
<key>Floor</key>
<value>4</value>
</attribute>
</extensible-attributes>

No

 Sample

$body

<items>
    <item>
        <target>
            <host>localhost</host>
            <user-name>admin</user-name>
            <password encryption-type="Base64">YWRtaW4=</password>
            <timeout-secs>120</timeout-secs>
        </target>
            <parameters>
            <record-type>SRV</record-type>
                    <query>
                            <srv-name> admin.demo.com</srv-name>
                            <srv-port>11</srv-port>
                            <srv-priority>10</srv-priority>
                            <srv-weight>10</srv-weight>
                            <srv-target> admin.demo.com</srv-target>
                            <dns-view>default</dns-view>
                    </query>
                    <update>
                            <srv-name> admin.demo.com</srv-name>
                            <srv-port>11</srv-port>
                            <srv-priority>10</srv-priority>
                            <srv-weight>10</srv-weight>
                            <srv-target> admin.demo.com</srv-target>
                            <dns-view>default</dns-view>
                            <comment>updated comment</comment>
                            <disable>true</disable>
                            <ttl>120</ttl>
                            <scheduled-at>2012-11-29T18:30:19+05:30</scheduled-at>
                            <extensible-attributes>
                            <attribute>
                                <key>Site</key>
                                <value>sample site</value>
                            </attribute>
                        </extensible-attributes>
                    </update>
           </parameters>
        </item>
&l<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>200 OK</title>
</head><body>
<h1>OK</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
</p>
</body></html>
Was this page helpful? Yes No Submitting... Thank you

Comments