• Buy Now
    • Rackspace Cloud
    • Email & Apps
    • Fanatical Support for AWS
    • Managed Google Cloud Platform
    • Office 365
  • Log In
    • MyRackspace Portal
    • Cloud Control Panel
    • Rackspace Webmail Login
    • Cloud Office Control Panel
  • Rackspace Logo
  • Developer Home
  • Developer Documentation
  • Blogs ▼
    • Technical Blog
    • Rackspace Blog
  • Support Documentation

Developer Docs


Let’s Build Something Powerful Together!

Submit an issue
  • Cloud DNS 1.0
  • Getting started
    • Get your credentials
    • Sending API requests to Cloud DNS
      • Convert cURL examples to run on Windows
    • Authenticate to the Rackspace Cloud
      • Authenticate by using cURL
      • Send an authentication request
      • Review the authentication response
      • Configure environment variables
    • Concepts
      • DNS
      • Domain
      • Subdomain
      • Record
      • Domain Owner
    • Create and manage DNS domains
      • Creating a new cloud server
      • Creating a domain
      • Listing domain details
      • Adding records
  • General API Information
    • Service access endpoints
    • DNS Service versions
      • Contract version
      • API version headers
    • Request and response types
    • Supported Record Types
      • Notes
      • Notes
    • Synchronous and asynchronous responses
      • Viewing status of all asynchronous job requests
    • IP Address Support
    • DNS propagation
    • Persistent Connections
    • Content Compression
    • Paginated collections
      • Pagination elements and attributes
    • Limits
      • Rate limits
      • Absolute limits
      • Retrieve account limits
    • Faults
    • Date and time format
    • Comments
    • Role-based access control (RBAC)
      • Assigning Roles to Account Users
      • Roles available for Rackspace Cloud DNS
      • Multiproduct global roles and permissions
      • Resolving conflicts between RBAC multiproduct and product-specific roles
      • RBAC permissions cross-reference to Rackspace Cloud DNS API operations
  • API reference
    • Limits operations
      • List limits
      • Show limits
      • List limit types
    • Domains operations
      • List domains
      • List domains by name
      • Create domain
      • Update domains
      • Delete domains
      • Delete domains and subdomains
      • Search domains
      • List domain details without subdomains
      • Show domain
      • Update domain
      • Delete domain
      • Delete domain and its subdomains
      • Show domain changes
      • Export domain
      • Clone domain
      • Import domain
    • Subdomains operations
      • List subdomains
    • Records operations
      • List records
      • Search records
      • Add records
      • Delete records
      • Update records
      • Delete record
      • Update record
      • Show record details
    • Reverse DNS operations
      • Update PTR records
      • Add PTR records
      • List PTR records
      • Delete PTR records
      • Show PTR record
  • Release notes
    • v1.0.34 Configuration Changes, October 24, 2014
      • What's new
      • Resolved issues
      • Known issues
    • v1.0.34, October 14, 2014
      • What's new
      • Resolved issues
      • Known issues
    • v1.0.33, July 29, 2014
      • What's new
      • Resolved issues
      • Known issues
    • v1.0.31 configuration changes, July 16, 2014
      • What's new
      • Resolved issues
      • Known issues
    • v1.0.31, June 26, 2014
      • What's new
      • Resolved issues
      • Known issues
  • Service updates
  • Additional resources
  • Disclaimer

Reverse DNS operations#

Use the reverse DNS API operations to view and manage the PTR records associated with a Rackspace cloud device.

Update PTR records#

PUT /v1.0/{account}/rdns

Updates one or more PTR records associated with a Rackspace Cloud device.

Note

This call returns an asynchronous response. Refer to Synchronous and asynchronous responses for more details and examples of the way that asynchronous responses work.

Note

The IP address (data) for a PTR record cannot be modified. To change the reverse DNS for a domain, any existing PTR record(s) must be deleted and new ones created.

Notice in the requests below that the service and device resource URI are specified respectively as the rel and href attributes of the link element.

This table shows the possible response codes for this operation:

Response Code Name Description
202 Accepted Request is accepted.
400 Bad Request The request is missing one or more elements, or the values of some elements are invalid.
400 500 dnsFault The DNS service has experienced a fault.
401 Unauthorized You are not authorized to complete this operation. This error can occur if the request is submitted with an invalid authentication token.
404 Not Found The requested item was not found.
413 Over Limit The number of items returned is above the allowed limit.
503 Service Unavailable The service is not available.

Request#

This table shows the header parameters for the request:

Name Type Description
X-Auth-Token String Arbitrary character string generated by the authentication service in response to valid credentials.

This table shows the URI parameters for the request:

Name Type Description
{account} String The tenant ID.

This operation does not accept a request body.

Example Update PTR record: XML request

PUT https://dns.api.rackspacecloud.com/v1.0/1234/rdns
Accept: application/xml
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/xml
Content-Length: 594

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rdns xmlns:ns2="http://www.w3.org/2005/Atom" xmlns="http://docs.rackspacecloud.com/dns/api/v1.0" xmlns:ns3="http://docs.rackspacecloud.com/dns/api/management/v1.0">
    <ns2:link href="https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321" rel="cloudServersOpenStack"></ns2:link>
    <recordsList>
        <record id="PTR-000000" type="PTR" name="bar.example.com" data="192.0.2.6" ttl="86500"/>
        <record id="PTR-000001" type="PTR" name="bar.example.com" data="2001:db8::6" ttl="86500"/>
    </recordsList>
</rdns>

Example Update PTR record: JSON request

PUT https://dns.api.rackspacecloud.com/v1.0/1234/rdns
Accept: application/json
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/json
Content-Length: 488

{
  "recordsList" : {
    "records" : [ {
      "name" : "bar.example.com",
      "id" : "PTR-000000",
      "type" : "PTR",
      "data" : "192.0.2.6",
      "ttl" : 86500
    }, {
      "name" : "bar.example.com",
      "id" : "PTR-000001",
      "type" : "PTR",
      "data" : "2001:db8::6",
      "ttl" : 86500
    } ]
  },
  "link" : {
    "content" : "",
    "href" : "https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321",
    "rel" : "cloudServersOpenStack"
  }
}

Response#

Example Update PTR record: XML response

Status: 200 OK
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/xml
Content-Length: 718

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rdns xmlns:ns2="http://www.w3.org/2005/Atom" xmlns="http://docs.rackspacecloud.com/dns/api/v1.0" xmlns:ns3="http://docs.rackspacecloud.com/dns/api/management/v1.0">
    <ns2:link href="https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321" rel="cloudServersOpenStack"></ns2:link>
    <recordsList>
        <record id="PTR-000000" type="PTR" name="bar.example.com" data="192.0.2.6" ttl="86500" updated="2011-09-22T01:12:51Z" created="2011-06-24T01:12:51Z"/>
        <record id="PTR-000001" type="PTR" name="bar.example.com" data="2001:db8::6" ttl="86500" updated="2011-09-22T01:12:51Z" created="2011-06-24T01:12:51Z"/>
    </recordsList>
</rdns>

Example Update PTR record: JSON response

Status: 200 OK
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/json
Content-Length: 688

{
  "recordsList" : {
    "records" : [ {
      "name" : "bar.example.com",
      "id" : "PTR-000000",
      "type" : "PTR",
      "data" : "192.0.2.6",
      "updated" : "2011-09-22T01:12:51.000+0000",
      "ttl" : 86500,
      "created" : "2011-06-24T01:12:51.000+0000"
    }, {
      "name" : "bar.example.com",
      "id" : "PTR-000001",
      "type" : "PTR",
      "data" : "2001:db8::6",
      "updated" : "2011-09-22T01:12:51.000+0000",
      "ttl" : 86500,
      "created" : "2011-06-24T01:12:51.000+0000"
    } ]
  },
  "link" : {
    "content" : "",
    "href" : "https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321",
    "rel" : "cloudServersOpenStack"
  }
}

Add PTR records#

POST /v1.0/{account}/rdns

Adds one or more PTR record records for a specified Cloud device.

Note

This call returns an asynchronous response. Refer to Synchronous and asynchronous responses for more details and examples of the way that asynchronous responses work.

Note

  • PTR records can only be added for Rackspace Cloud Servers and Load Balancers.

  • The id for the record must not be specified.

  • For First Generation Cloud Servers, when the server is created, each public IPv4 address that comes with the server usually has a default PTR record already created for it. A request to list the PTR records associated with the server should return any PTR records for the server. If a default PTR record exists, the default PTR record can be appropriately modified or deleted and an appropriate PTR record created.

    If an attempt to add a PTR record for the public IP address of a newly created First Generation Cloud Server results in a 400 Bad Request error message, that is an indication that a default PTR record for the IP address already exists.

  • Adding PTR records for IPv6 addresses is supported only for Cloud Servers.

Notice in the requests below that the service and device resource URI are specified respectively as the rel and href attributes of the link element, as follows:

  • rel – this is the name of the service (as provided in the serviceCatalog from Identity) from where the device was created.
  • href – this is the URL to the device for which the PTR record is associated. It was returned when the device was created and it uniquely identifies the device.
  • content – this is currently a place holder for possible future use.

This table shows the possible response codes for this operation:

Response Code Name Description
200 Success Request succeeded.
400 Bad Request The request is missing one or more elements, or the values of some elements are invalid.
400 500 dnsFault The DNS service has experienced a fault.
401 Unauthorized You are not authorized to complete this operation. This error can occur if the request is submitted with an invalid authentication token.
404 Not Found The requested item was not found.
413 Over Limit The number of items returned is above the allowed limit.
503 Service Unavailable The service is not available.

Request#

This table shows the header parameters for the request:

Name Type Description
X-Auth-Token String Arbitrary character string generated by the authentication service in response to valid credentials.

This table shows the URI parameters for the request:

Name Type Description
{account} String The tenant ID.

This operation does not accept a request body.

Example Add PTR record: XML request

POST https://dns.api.rackspacecloud.com/v1.0/1234/rdns
Accept: application/xml
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/xml
Content-Length: 554

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rdns xmlns:ns2="http://www.w3.org/2005/Atom" xmlns="http://docs.rackspacecloud.com/dns/api/v1.0" xmlns:ns3="http://docs.rackspacecloud.com/dns/api/management/v1.0">
    <ns2:link href="https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321" rel="cloudServersOpenStack"></ns2:link>
    <recordsList>
        <record type="PTR" name="example.com" data="192.0.2.7" ttl="56000"/>
        <record type="PTR" name="example.com" data="2001:db8::7" ttl="56000"/>
    </recordsList>
</rdns>

Example Add PTR record: JSON request

POST https://dns.api.rackspacecloud.com/v1.0/1234/rdns
Accept: application/json
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/json
Content-Length: 426

{
  "recordsList" : {
    "records" : [ {
      "name" : "example.com",
      "type" : "PTR",
      "data" : "192.0.2.7",
      "ttl" : 56000
    }, {
      "name" : "example.com",
      "type" : "PTR",
      "data" : "2001:db8::7",
      "ttl" : 56000
    } ]
  },
  "link" : {
    "content" : "",
    "href" : "https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321",
    "rel" : "cloudServersOpenStack"
  }
}

Response#

Example Add PTR record: XML response

Status: 200 OK
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/xml
Content-Length: 710

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rdns xmlns:ns2="http://www.w3.org/2005/Atom" xmlns="http://docs.rackspacecloud.com/dns/api/v1.0" xmlns:ns3="http://docs.rackspacecloud.com/dns/api/management/v1.0">
    <ns2:link href="https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321" rel="cloudServersOpenStack"></ns2:link>
    <recordsList>
        <record id="PTR-000002" type="PTR" name="example.com" data="192.0.2.7" ttl="56000" updated="2011-09-24T01:12:51Z" created="2011-09-24T01:12:51Z"/>
        <record id="PTR-000003" type="PTR" name="example.com" data="2001:db8::7" ttl="56000" updated="2011-09-24T01:12:51Z" created="2011-09-24T01:12:51Z"/>
    </recordsList>
</rdns>

Example Add PTR record: JSON response

Status: 200 OK
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/json
Content-Length: 680

{
  "recordsList" : {
    "records" : [ {
      "name" : "example.com",
      "id" : "PTR-000002",
      "type" : "PTR",
      "data" : "192.0.2.7",
      "updated" : "2011-09-24T01:12:51.000+0000",
      "ttl" : 56000,
      "created" : "2011-09-24T01:12:51.000+0000"
    }, {
      "name" : "example.com",
      "id" : "PTR-000003",
      "type" : "PTR",
      "data" : "2001:db8::7",
      "updated" : "2011-09-24T01:12:51.000+0000",
      "ttl" : 56000,
      "created" : "2011-09-24T01:12:51.000+0000"
    } ]
  },
  "link" : {
    "content" : "",
    "href" : "https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321",
    "rel" : "cloudServersOpenStack"
  }
}

List PTR records#

GET /v1.0/{account}/rdns/{service-name}

Lists all PTR records configured for a specified Cloud device.

This call lists all PTR records configured for a specified Cloud device.

This table shows the possible response codes for this operation:

Response Code Name Description
200 Success Request succeeded.
400 Bad Request The request is missing one or more elements, or the values of some elements are invalid.
500 dnsFault The DNS service has experienced a fault.
401 Unauthorized You are not authorized to complete this operation. This error can occur if the request is submitted with an invalid authentication token.
404 Not Found The requested item was not found.
413 Over Limit The number of items returned is above the allowed limit.
503 Service Unavailable The service is not available.

Request#

This table shows the URI parameters for the request:

Name Type Description
{account} String The tenant ID.
{service-name} String Name of the Cloud service.

This table shows the query parameters for the request:

Name Type Description
href String Device-resource-uri for the specified Cloud device.

This operation does not accept a request body.

Example List PTR records: XML request

GET https://dns.api.rackspacecloud.com/v1.0/1234/rdns/cloudServersOpenStack?href=https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321
Accept: application/xml
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/xml
Content-Length: 0

Example List PTR records: JSON request

GET https://dns.api.rackspacecloud.com/v1.0/1234/rdns/cloudServersOpenStack?href=https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321
Accept: application/json
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/json
Content-Length: 0

Response#

Example List PTR records: XML response

Status: 200 OK
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/xml
Content-Length: 710

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rdns xmlns:ns2="http://www.w3.org/2005/Atom" xmlns="http://docs.rackspacecloud.com/dns/api/v1.0" xmlns:ns3="http://docs.rackspacecloud.com/dns/api/management/v1.0">
    <ns2:link href="https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321" rel="cloudServersOpenStack"></ns2:link>
    <recordsList>
        <record id="PTR-000000" type="PTR" name="example.com" data="192.0.2.6" ttl="56000" updated="2011-06-24T01:12:51Z" created="2011-06-24T01:12:51Z"/>
        <record id="PTR-000001" type="PTR" name="example.com" data="2001:db8::6" ttl="56000" updated="2011-06-24T01:12:51Z" created="2011-06-24T01:12:51Z"/>
    </recordsList>
</rdns>

Example List PTR records: JSON response

Status: 200 OK
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/json
Content-Length: 680

{
  "recordsList" : {
    "records" : [ {
      "name" : "example.com",
      "id" : "PTR-000000",
      "type" : "PTR",
      "data" : "192.0.2.6",
      "updated" : "2011-06-24T01:12:51.000+0000",
      "ttl" : 56000,
      "created" : "2011-06-24T01:12:51.000+0000"
    }, {
      "name" : "example.com",
      "id" : "PTR-000001",
      "type" : "PTR",
      "data" : "2001:db8::6",
      "updated" : "2011-06-24T01:12:51.000+0000",
      "ttl" : 56000,
      "created" : "2011-06-24T01:12:51.000+0000"
    } ]
  },
  "link" : {
    "content" : "",
    "href" : "https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321",
    "rel" : "cloudServersOpenStack"
  }
}

Delete PTR records#

DELETE /v1.0/{account}/rdns/{service-name}

Deletes one or all PTR records associated with a Rackspace Cloud device. Use the optional ip query parameter to specify a specified record to delete. Omitting this parameter, deletes all PTR records associated with a specified device.

Note

This call returns an asynchronous response, as described in Synchronous and asynchronous responses.

This table shows the possible response codes for this operation:

Response Code Name Description
202 Accepted Request is accepted.
400 Bad Request The request is missing one or more elements, or the values of some elements are invalid.
400 500 dnsFault The DNS service has experienced a fault.
401 Unauthorized You are not authorized to complete this operation. This error can occur if the request is submitted with an invalid authentication token.
404 Not Found The requested item was not found.
413 Over Limit The number of items returned is above the allowed limit.
503 Service Unavailable The service is not available.

Request#

This table shows the URI parameters for the request:

Name Type Description
{account} String The tenant ID.
{service-name} String Name of the Cloud service.

This table shows the query parameters for the request:

Name Type Description
href String Device-resource-uri for the specified Cloud device.
ip String IP address for the specified Cloud device.

This operation does not accept a request body.

Example Delete PTR records: XML request

DELETE https://dns.api.rackspacecloud.com/v1.0/1234/rdns/cloudServersOpenStack?href=https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321
Accept: application/xml
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/xml
Content-Length: 0

Example Delete PTR records: JSON request

DELETE https://dns.api.rackspacecloud.com/v1.0/1234/rdns/cloudServersOpenStack?href=https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321
Accept: application/json
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/json
Content-Length: 0

Example Delete PTR record: XML request

DELETE https://dns.api.rackspacecloud.com/v1.0/1234/rdns/cloudServersOpenStack?href=https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321&ip=2001:db8::6
Accept: application/xml
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/xml
Content-Length: 0

Example Delete PTR record: JSON request

DELETE https://dns.api.rackspacecloud.com/v1.0/1234/rdns/cloudServersOpenStack?href=https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321&ip=2001:db8::6
Accept: application/json
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/json
Content-Length: 0

Response#

Example Delete PTR records: XML response

Status: 202 Accepted
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/xml
Content-Length: 475

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<asyncresponse xmlns:ns2="http://www.w3.org/2005/Atom" xmlns="http://docs.rackspacecloud.com/dns/api/v1.0" xmlns:ns3="http://docs.rackspacecloud.com/dns/api/management/v1.0">
<callbackUrl>https://dns.api.rackspacecloud.com/v1.0/440370/status/aad311e0-a465-4323-8d53-3d2f8ce5c372</callbackUrl>
<jobId>aad311e0-a465-4323-8d53-3d2f8ce5c372</jobId>
    <requestUrl>https://dns.api.rackspacecloud.com/v1.0/440370/rdns/cloudServers?href=https://dfw.servers.api.rackspacecloud.com/v1.0/440370/servers/264111</requestUrl>
<status>RUNNING</status>
<verb>DELETE</verb>
</asyncresponse>

Example Delete PTR records: JSON response

Status: 202 Accepted
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/json
Content-Length: 376


{
  "status": "RUNNING",
  "verb": "DELETE",
  "jobId": "aad311e0-a465-4323-8d53-3d2f8ce5c372",
  "callbackUrl": "https://dns.api.rackspacecloud.com/v1.0/440370/status/aad311e0-a465-4323-8d53-3d2f8ce5c372",
  "requestUrl": "https://dns.api.rackspacecloud.com/v1.0/440370/rdns/cloudServers?href=https://dfw.servers.api.rackspacecloud.com/v1.0/440370/servers/264111"
}

Example Delete PTR record: XML response

Status: 202 Accepted
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/xml
Content-Length: 475

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<asyncresponse xmlns:ns2="http://www.w3.org/2005/Atom" xmlns="http://docs.rackspacecloud.com/dns/api/v1.0" xmlns:ns3="http://docs.rackspacecloud.com/dns/api/management/v1.0">
<callbackUrl>https://dns.api.rackspacecloud.com/v1.0/440370/status/aad311e0-a465-4323-8d53-3d2f8ce5c372</callbackUrl>
<jobId>aad311e0-a465-4323-8d53-3d2f8ce5c372</jobId>
<requestUrl>https://dns.api.rackspacecloud.com/v1.0/440370/rdns/cloudServers?href=https://dfw.servers.api.rackspacecloud.com/v1.0/440370/servers/264111</requestUrl>
<status>RUNNING</status>
<verb>DELETE</verb>
</asyncresponse>

Example Delete PTR record: JSON response

Status: 202 Accepted
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/json
Content-Length: 376


{
  "status": "RUNNING",
  "verb": "DELETE",
  "jobId": "aad311e0-a465-4323-8d53-3d2f8ce5c372",
  "callbackUrl": "https://dns.api.rackspacecloud.com/v1.0/440370/status/aad311e0-a465-4323-8d53-3d2f8ce5c372",
  "requestUrl": "https://dns.api.rackspacecloud.com/v1.0/440370/rdns/cloudServers?href=https://dfw.servers.api.rackspacecloud.com/v1.0/440370/servers/264111"
}

Show PTR record#

GET /v1.0/{account}/rdns/{service-name}/{recordId}

Shows details for a specified PTR record associated with a specified Cloud device.

This call shows details for a specified PTR record associated with a specified cloud device.

This table shows the possible response codes for this operation:

Response Code Name Description
200 Success Request succeeded.
400 Bad Request The request is missing one or more elements, or the values of some elements are invalid.
400 500 dnsFault The DNS service has experienced a fault.
401 Unauthorized You are not authorized to complete this operation. This error can occur if the request is submitted with an invalid authentication token.
404 Not Found The requested item was not found.
413 Over Limit The number of items returned is above the allowed limit.
503 Service Unavailable The service is not available.

Request#

This table shows the URI parameters for the request:

Name Type Description
{account} String The tenant ID.
{service-name} String Name of the Cloud service.
{recordId} String ID for the record.

This table shows the query parameters for the request:

Name Type Description
href String Device-resource-uri for the specified Cloud device.

This operation does not accept a request body.

Example List PTR record details: XML request

GET https://dns.api.rackspacecloud.com/v1.0/1234/rdns/cloudServersOpenStack/PTR-000000?href=https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321
Accept: application/xml
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/xml
Content-Length: 0

Example List PTR record details: JSON request

GET https://dns.api.rackspacecloud.com/v1.0/1234/rdns/cloudServersOpenStack/PTR-000000?href=https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321
Accept: application/json
X-Auth-Token: ea85e6ac-baff-4a6c-bf43-848020ea3812
Content-Type: application/json
Content-Length: 0

Response#

Example List PTR record details: XML response

Status: 200 OK
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/xml
Content-Length: 553

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rdns xmlns:ns2="http://www.w3.org/2005/Atom" xmlns="http://docs.rackspacecloud.com/dns/api/v1.0" xmlns:ns3="http://docs.rackspacecloud.com/dns/api/management/v1.0">
    <ns2:link href="https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321" rel="cloudServersOpenStack"></ns2:link>
    <recordsList>
        <record id="PTR-000000" type="PTR" name="example.com" data="192.0.2.6" ttl="56000" updated="2011-06-24T01:12:51Z" created="2011-06-24T01:12:51Z"/>
    </recordsList>
</rdns>

Example List PTR record details: JSON response

Status: 200 OK
Date: Thu, 28 Jul 2011 21:54:21 GMT
X-API-VERSION: 1.0.17
Content-Type: application/json
Content-Length: 442

{
  "recordsList" : {
    "records" : [ {
      "name" : "example.com",
      "id" : "PTR-000000",
      "type" : "PTR",
      "data" : "192.0.2.6",
      "updated" : "2011-06-24T01:12:51.000+0000",
      "ttl" : 56000,
      "created" : "2011-06-24T01:12:51.000+0000"
    } ]
  },
  "link" : {
    "content" : "",
    "href" : "https://dfw.servers.api.rackspacecloud.com/v2/1234/servers/0987654321",
    "rel" : "cloudServersOpenStack"
  }
}
Previous Records operations
Next Release notes
Docs
  • Style Guide for Technical Content
  • Cloud Backup
  • Cloud Block Storage
  • Cloud Databases
  • Cloud DNS
  • Cloud Files
  • Identity
  • Cloud Images
  • Cloud Load Balancers
  • Cloud Monitoring
  • Cloud Orchestration
  • Cloud Networks
  • Cloud Queues
  • Cloud Servers
  • Rackspace Auto Scale
  • Rackspace CDN
Sdks
  • Go
  • Java
  • .Net
  • Node
  • PHP
  • Python
  • Ruby
Partner Tools
  • Airbrake
  • Mailgun
  • ObjectRocket
  • RedisToGo
Blog
  • Technical Blog
  • Rackspace Blog
©2019 Rackspace US, Inc.
  • ©2019 Rackspace US, Inc.
  • About Rackspace
  • Investors
  • Careers
  • Privacy Statement
  • Website Terms
  • Trademarks