Frequently asked questions

Find answers to frequently asked questions about the DOM application.

Is domain validation mandatory?
Currently, domain validation is optional at launch. DOM checks will not be enforced, allowing you to familiarize with the process. DOM will be gradually enforced, with mandatory domain validation as a prerequisite for all hostnames being onboarded. New customers will be automatically enrolled in the enforced mode, and existing customers will gradually be transitioned to enforced mode.

Do I need to validate existing/active hostnames?
No, you don’t. Existing hostnames that are currently active in a Property Manager configuration are considered validated. Hostnames are validated at the HOST level. Wildcards are validated at the DOMAIN level. The new validation process only applies to newly added domains, or if one of those existing hostnames is moved to a different property.

How can I monitor the validation status?
The DOM UI lists all the domains submitted for validation with their current status. To view details about the domain, its validation and the status history, click the Action menu icon and click View Details.

Why is the domain status stuck in the Validation in Progress state?
DOM background jobs are continuously trying to verify the token. Wait for the next job run for the validation to complete. If the domain status is stuck for over 30 minutes, here are possible reasons:

• You haven’t updated your DNS or HTTP server yet, or you have used an incorrect token. Use the token you got from the DOM UI or API and wait for the next run of the DOM background jobs.
• In case of DNS record update, the TTL (time to live) of the DNS cache is too large. Having a smaller TTL on the DNS record helps DOM to validate the records faster.
• In case of HTTP validation, there is a known issue on Linux machines. If you have created a file containing the token using vim editor, the file may contain an additional newline character that you haven’t added explicitly. To get around this, use the command echo -n "<token>" > <file_name> to create the file with the token on your HTTP server.

What are the different levels of validations?
You can do the validation for a HOST (exact domain), WILDCARD (one level of subdomains) and DOMAIN (entire domain, that is all levels of subdomains). Read more.

Does the validation token have an expiration?
Yes, you need to complete the validation process in that timeframe. View the domain details to check the expiration date. If your token has expired, resubmit your domain for validation to get a new token.

Does a completed validation expire?
Once you’ve completed a validation, there is no revalidation necessary or expiration.

Why can’t I see some action buttons in the DOM UI?
Access to the DOM UI is controlled by permissions. If you have read-only access, you can see a list of domains and monitor their status, but you don’t see the action buttons. If you have write permissions, you can submit a domain for validation. If you have delete permissions, you can invalidate and delete domains. The permissions are:

• domainValidationRead. Grants read-only access to the DOM UI. Users with this permission can view submitted domains and their validation status, but cannot make changes.
• domainValidationWrite. Grants write access to the UI. Required to submit new domains for validation and to validate domain validation via DNS or HTTP methods.
• domainValidationDelete. Grants the ability to invalidate or delete a domain from the system. Used when a domain is no longer needed or ownership has changed.

Can I validate a hostname (sub-domain) if another account has already validated the top-level?
Yes, both accounts would go through the validation process for each of the hostnames separately.

Can a hostname be validated on two accounts at the same time, for example for transfer purpose?
Yes, multiple accounts can have a validation record for the same domain, but only one account is allowed to add or activate it in a configuration.

Do I have to repeat the validation if I move a hostname from one configuration to another within the same account?
No, you don’t need to repeat the validation. DOM has an account-level scope.

What happens when a whole configuration is moved to another account?
You don’t need to repeat domain validation as the hostname is already active.

If a hostname active in an account is added in another account, what will happen?
This situation is not allowed and you’ll see an error.

Has the process changed when moving a single hostname from one account to another, without moving the whole configuration?
Transferring a hostname between accounts (i.e.: inter-account hostname move) has not changed. You need to perform validation on every step where you add a hostname. Read more about migrating hostname between accounts .