Domain verification works with www.domain.com but not with domain.com. Problem?

Ted McClellan

I had to enter www.domaindomain.com. Will this cause a problem? 

Will any of this take effect?

What happens if I don't do anything? If we still can't verify your domain after a few weeks, your domain will be marked as Unverified. This means:

• If you've configured SAML or set a password policy it won't apply to your users anymore.
• Your users will have control of their email address and other details.
• Your users will only be able to login using their Atlassian account username/password.

AnnWorley

Judging from this paragraph in Domain verification, the www shouldn't cause an issue:

"HTTPS is mandatory for hosting the HTML file, and it needs to be a valid SSL certificate from a certificate authority (self-signed certificates won't work). Only one redirection to a www domain prefix is allowed. For example, if your domain is @example.com, domains can only be successfully verified on https://example.com or https://www.example.com. You can't verify domains that redirect to a second domain."

Please let me know what obstacle you ran into when you tried to verify the domain without the www prefix. At what point did the verification fail?