Configuring Route53Domains

To configure Route53Domains:
  1. Go to DDI+ > INTEGRATION HUB, and then click Add new vendor.
    The Select vendor page is displayed.
  2. On the Select Vendor page, click Route53Domains.
  3. On the Vendor Configuration page, under the Information section, enter or select the required field information.
    The following table describes the various fields in this section:
    Field Description
    *Name Enter a unique name to identify the vendor account which is being configured.
    Description Enter a description for the purpose of configuring this vendor, if required.
    Data center Select a data center from the options available in the dropdown list.
    *: Mandatory fields
  4. On the Vendor Configuration page, under the Credentials section, enter or select the required field information.
    The following table describes the various fields in this section:
    Field Description
    Auth type Displays the AWS signature method of authentication selected by default.
    *Access Key Enter the Access Key provided by route53domains.
    *AWS Region Enter the region which is receiving the request.
    Session Token Enter the session token which is only required when using temporary security credentials.
    *URL Enter API URL for the vendor with the HTTPS/HTTP protocol
    *Secret Key Enter the Secret Key provided by route53domains.
    *Service Name This field is filled by default. The service which is receiving a request.
    *: Mandatory fields
  5. Enable Config sync for parsing the vendor
  6. On the Vendor Configuration page, under the Configurations section, turn on the Enable Config toggle to add additional vendor configuration attributes.
    Sample Schema:
    {
        "businessUnits": [
            "Sales",
            "Marketing",
            "Finance"
        ],
        "domain_price_limit": 10,
        "approver_email": "[email protected]",
        "nameServerConfig": [
            {
                "supported_domains": [
                    ".com",
                    ".org",
                    ".in",
                    ".biz"
                ],
                "auto_fetch": false,
                "vendor": "",
                "vendor_account_name": "",
                "nameservers": [
                    "test1.ns.com",
                    "test2.ns.com"
                ]
            },
            {
                "supported_domains": [
                    ".net",
                    ".info"
                ],
                "auto_fetch": false,
                "vendor": "SampleVendor",
                "vendor_account_name": "SampleVendorAccount",
                "nameservers": []
            }
        ],
        "contacts": {
            "AdminContact": {
                "FirstName": "Sample Name",
                "MiddleName": "Sample Name",
                "LastName": "Sample Name",
                "ContactType": "Sample Type",
                "OrganizationName": "Sample Organization",
                "AddressLine1": "Sample Address",
                "AddressLine2": "Sample Address",
                "City": "Sample City",
                "State": "Sample State",
                "CountryCode": "Sample Code",
                "ZipCode": "Sample Code",
                "PhoneNumber": "Sample Phone",
                "Email": "Sample Email",
                "Fax": "Sample Fax"
            },
            "RegistrantContact": {
                "FirstName": "Sample Name",
                "MiddleName": "Sample Name",
                "LastName": "Sample Name",
                "ContactType": "Sample Type",
                "OrganizationName": "Sample Organization",
                "AddressLine1": "Sample Address",
                "AddressLine2": "Sample Address",
                "City": "Sample City",
                "State": "Sample State",
                "CountryCode": "Sample Code",
                "ZipCode": "Sample Code",
                "PhoneNumber": "Sample Phone",
                "Email": "Sample Email",
                "Fax": "Sample Fax"
            },
            "TechContact": {
                "FirstName": "Sample Name",
                "MiddleName": "Sample Name",
                "LastName": "Sample Name",
                "ContactType": "Sample Type",
                "OrganizationName": "Sample Organization",
                "AddressLine1": "Sample Address",
                "AddressLine2": "Sample Address",
                "City": "Sample City",
                "State": "Sample State",
                "CountryCode": "Sample Code",
                "ZipCode": "Sample Code",
                "PhoneNumber": "Sample Phone",
                "Email": "Sample Email",
                "Fax": "Sample Fax"
            }
        },
        "PrivacyProtectAdminContact": true,
        "PrivacyProtectRegistrantContact": true,
        "PrivacyProtectTechContact": true
    }

    The following table explains the strings in the JSON schema:

    Table 1.
    Strings Description
    PrivacyProtectAdminContact Whether you want to conceal contact information from WHOIS queries. If you specify true, WHOIS ("who is") queries return contact information for the registrar, the phrase "REDACTED FOR PRIVACY", or "On behalf of domain name's owner."
    PrivacyProtectRegistrantContact Whether you want to conceal contact information from WHOIS queries. If you specify true, WHOIS ("who is") queries return contact information either for Amazon Registrar (for .com, .net, and .org domains) or for our registrar associate, Gandi (for all other TLDs). If you specify false, WHOIS queries return the information that you entered for the registrant contact (domain owner).
    PrivacyProtectTechContact Whether you want to conceal contact information from WHOIS queries. If you specify true, WHOIS ("who is") queries return contact information either for Amazon Registrar (for .com, .net, and .org domains) or for our registrar associate, Gandi (for all other TLDs). If you specify false, WHOIS queries return the information that you entered for the technical contact.
    AdminContact Provides detailed contact information.
    RegistrantContact Provides detailed contact information.
    TechContact Provides detailed contact information.
    domain_price_limit The domain_price_limit field serves to establish a threshold price for domain registrations. If the cost of a domain surpasses the value set in domain_price_limit, explicit approval is mandated for the registration. If the domain's price falls below the domain_price_limit, no approval is necessary.
    approver_email The approver_email field is to trigger an email notification for approval when the price of a domain registration exceeds the specified domain_price_limit. If the cost surpasses this limit, an email is automatically sent to the designated approver for review and confirmation
    nameServerConfig The nameServerConfig field is configured to facilitate the automatic selection of nameservers based on predefined conditions during the domain registration process
    supported_domains Explicitly define the list of Top-Level Domains (TLDs) permitted for use in the domain procurement process, particularly when configured nameservers are in use. Like [".com", ".net" ]
    auto_fetch The auto_fetch used to automatically retrieve the name server information from the configured name server account in AppViewX.
    vendor The vendor field is to specify the DNS vendor from which the name server should be automatically fetched. This is applicable only if the auto fetch is true.
    vendor_account_name The vendor_account_name field is used to specify vendor account name configured in AppViewX, specifically for automatically fetching the nameserver. This configuration is applicable only when the auto_fetch flag is set to true
    nameservers The nameservers is used to specify the list of all the nameservers to be assigned during the domain registration. This is applicable only when the auto_fetch flag is set to false. like ["example1.ns.com", "example2.ns.com"].
    *: Mandatory fields
  7. Click Finish.