Case Study - Global Reach, Local Touch: The Role of GeoDNS in eCommerce Expansion

Is DNSSEC available

Description

Check is DNSSEC available for a specific DNS zone.


Parameters

Name Data Type Status Description
auth-id or sub-auth-id or sub-auth-user Integer Required Authentication parameter
auth-password String Required Authentication parameter
domain-name String Required Domain name or reverse zone name for which you would like to check is DNSSEC available 

Return: 1 if DNSSEC is available for this zone and 0 if it is not.


Errors

When the authenctication of API user is not correct, any API request will fail with the following status and statusDescription:

{"status":"Failed","statusDescription":"Invalid authentication, incorrect auth-id or auth-password."}

In case the credentials of API sub user are invalid, the following status and statusDescription will be returned:

{"status":"Failed","statusDescription":"Invalid authentication, incorrect sub-auth-id, sub-auth-user or auth-password."}

If you have entered an invalid or non-existent domain name,the following status will be returned:

{"status":"Failed","statusDescription":"Missing domain-name"}

Note: These are example errors in JSON format, if there are missing or wrong parameters, an error will be displayed again.



Example

URL JSON: https://api.cloudns.net/dns/is-dnssec-available.json
POST/GET: auth-id=0&auth-password=password&domain-name=example.com
POST/GET: sub-auth-id=0&auth-password=password&domain-name=example.com

URL XML: https://api.cloudns.net/dns/is-dnssec-available.xml
POST/GET: auth-id=0&auth-password=password&domain-name=example.com
POST/GET: sub-auth-id=0&auth-password=password&domain-name=example.com

 


Last modified: 2019-06-17
Cookies help us deliver our services. By using our services, you agree to our use of cookies. Learn more