GET - GET a specific PTR Record by ID

Purpose

This API retrieves a specific PTR (Pointer) record under a DNS zone. PTR records are used for reverse DNS lookups, mapping IP addresses to domain names for network verification and authentication. It provides critical insight into reverse DNS configurations, ensuring proper authentication, security, and monitoring of network resources.

Request URL

Method: GET

https://{appconsole_IP}:{9443}/api/dhcp/zone/{zone_pk}/PTR/{pk}/

Request Headers

The following headers must be included in the API request for successful authentication and data submission:

Authorization: DDI Central's OAuth implementation uses the Bearer authentication scheme. Hence, while making API calls, access_token obtained via the OAuth 2.0 Client Credentials Grant must be included in the Authorization header of API requests. This token verifies the client’s identity and ensures appropriate permissions for accessing resources.

The Authorization Header follows the format below:

headers = { "Authorization": "Bearer {bearer_tk}" }


Content-Type: Required in the header to indicate the media type of the resource being sent. It helps the server at the receiving end understand how to process the transmitted request body.

The Content-Type Header follows the format below:

headers ={ "Content-Type": "application/json" }

Path Parameters

  • zone_pk* long
    • The unique identifier of the DNS zone where the PTR record exists.
    • Example: 5867.
  • pk* long
    • The unique identifier of the specific PTR record to retrieve.
    • Example: 10805.

 

* - Mandatory parameter.

 

Sample Response

Copied
{
   "ptr_domain_id":554,
   "zone_id":5867,
   "domain_name":"he.hellotest109.com.",
   "domain_ttl":8640,
   "zone_name":"hellotest109.com.",
   "cluster_name":"wincluster-zoho",
   "records":[
      "data.com.",
      "data1.com.",
      "data2.com.",
      "data3.com.",
      "data4.com.",
      "data5.com.",
      "data6.com.",
      "data7.com."
   ]
}