Company Domain Validation Failed

Develop, Build & Integrate APIs & Integrations
,
1

Hey,

Trying to validate a company domain for an app we are looking to publish, it initially validates successfully, then about 10 minutes later, go back to the “company info” page, it says there was a problem validating it and to contact support.

Unfrotunately Support is away this week, has anyone else experienced this?

Thanks

2

Hi @DMcAssey

The issue may be attributed to a DNS propagation delay, which can occur when changes to DNS records, such as MX records for email validation, take time to spread across the internet. This delay could explain why the validation was initially successful but later failed.

To resolve this, try waiting for 24-48 hours to allow the DNS changes to fully propagate, then attempt re-validating the domain.

Also, ensure that your DNS records, specifically the MX records for email validation, are set up correctly according to HubSpot’s instructions. Double-checking your DNS records can help identify and resolve any configuration issues.

Refer the help article - Connect your domain to HubSpot

Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards

3

Hi, thanks for the response.

I have tried waiting, this started happening at the start of last week, unfortunately what I have found is that the validation code changes when the validation fails, which then causes the validation to never pass.

Would it be worth reducing the TTL for the TXT record to 60 seconds, to reduce the propagation delay?

4

Temporarily setting the TTL to a low number (60 seconds), I was able to update the key, and validate the domain. Thank you

5

@DMcAssey thank you for sharing this solution, I’m glad it’s working!

6

Hi @DMcAssey I was helping someone earlier last week with a similar issue here, I’m not sure if it was resolved.

7

Hi Jennifer,

Thanks for the reply, I am able to verify it, but it only stays verifeid for about 10-15 minutes, before reverting back to an error “Cannot verify Domain, contact support or try again”.

We use AWS Route53 for our DNS

Thanks,

Dan