Ascio Web Service v3

SOAP CreateDnsSecKey

Always get the right IP-address

DNSSEC is an extension to DNS that enables clients (like a web browser) to make sure that it is accessing the domain that wants to access.

DNSSEC was designed to protect clients from forged DNS data.

When a DNSSEC-enabled name server is responding to a query for a domain that is DNSSEC-enabled, it digitally signs the response, allowing the client to verify the authenticity of the response. AWS allows you to register domains that are DNSSEC-enabled with the NIC. Note that the relevant NIC needs to support DNSSEC for this to happen.

You do this by creating DNSSEC Key Objects (handles), and you then specify up to five of these on your orders.

At the time of writing, AWS only supports DNSSEC for .SE, .FI, .EU, .NL.

Refer to the relevant TLD Kits for additional information. Also see the documentation for the DnsSecKey object in this document.

Additional reading: http://en.wikipedia.org/wiki/Dnssec 

CreateDnsSecKeyResponse CreateDnsSecKey(SecurityHeaderDetails securityHeader,CreateDnsSecKeyRequest request)

Response codes

ResultCodeMessageValue
200OK
401Authorization failed
501Syntax error in parameters or arguments
506Required attribute missing in request

CreateDnsSecKey Request

Property
request

CreateDnsSecKeyResponse

PropertyDescription
CreateDnsSecKeyResult
DnsSecKey
ResultCodeExample: 1
ResultMessage
Errors

Used in Classes

Open in Code Generator

SOAP example

<soapenv:Envelope xmlns:arr="http://schemas.microsoft.com/2003/10/Serialization/Arrays" xmlns:service="http://www.ascio.com/2013/02/AscioService" xmlns:v3="http://www.ascio.com/2013/02" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Header>
        <v3:SecurityHeaderDetails>
            <v3:Account>${#Project#Account}</v3:Account>
            <v3:Password>${#Project#Password}</v3:Password>
        </v3:SecurityHeaderDetails>
        <v3:ImpersonationHeaderDetails>
            <v3:TransactionAccount>${#Project#TransactionAccount}</v3:TransactionAccount>
        </v3:ImpersonationHeaderDetails>
    </soapenv:Header>
    <soapenv:Body>
        <service:CreateDnsSecKey>
            <service:request>
                <v3:DnsSecKey>
                    <v3:Handle>JD123</v3:Handle>
                    <v3:Status>StatusTest</v3:Status>
                    <v3:DigestAlgorithm>RSA-SHA256</v3:DigestAlgorithm>
                    <v3:DigestType>SHA-256</v3:DigestType>
                    <v3:Digest>846E5ED4AB6788032B89393619752F662CF2B7B2046A8EC0804DF88F1469AC1E</v3:Digest>
                    <v3:Protocol>ProtocolTest</v3:Protocol>
                    <v3:KeyType>KeyTypeTest</v3:KeyType>
                    <v3:KeyAlgorithm>KeyAlgorithmTest</v3:KeyAlgorithm>
                    <v3:KeyTag>2224</v3:KeyTag>
                    <v3:PublicKey>PublicKeyTest</v3:PublicKey>
                </v3:DnsSecKey>
            </service:request>
        </service:CreateDnsSecKey>
    </soapenv:Body>
</soapenv:Envelope>
Download libraries and examples
WSDL for AWS v3
https://aws.demo.ascio.com/v3/aws.wsdl (OTE)
https://aws.ascio.com/v3/aws.wsdl (Live)
Please configure the IP-Whitelisting in the portal/demo-portal.