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

[Ted McClellan]

I had to enter www.domain.com for the domain verification to work but our users have email addresses that include just @domain.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?

[Ted McClellan]

if we simply try to verify the https://domain.com it fails to find the file and displays a browser error. When we try https://www.domain.com it works and successfully verifies the domain. 

[AnnWorley]

Wild guess - is domain.com in DNS without the www?

I asked around the Cloud team and everyone reads that "For example, if your domain is @example.com, domains can only be successfully verified on https://example.com or https://www.example.com. " as meaning the www is ok. I have never seen www on an email address so your situation cannot be unique.

[Michael Hyland]

I am facing the exact same issue.

@a_gasovich - can I ask how this was resolved?