# Verify domain doesn't work properly

**URL:** <https://community.hubspot.com/t/verify-domain-doesnt-work-properly/78977>\
**Category:** Blog, Website & Page Publishing\
**Tags:** developer-tools\
**Created:** [April 10, 2023, 11:36am UTC](https://community.hubspot.com/t/verify-domain-doesnt-work-properly/78977 "2023-04-10T11:36:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dayschedule](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@dayschedule](https://community.hubspot.com/u/dayschedule)\
**Post date:** [April 10, 2023, 11:36am UTC](https://community.hubspot.com/t/verify-domain-doesnt-work-properly/78977/1 "2023-04-10T11:36:26Z")

</div>

We’ve added the TXT recored for our domain [dayschedule.com](https://dayschedule.com/) AWS, and the value is populating fine on all DNS checker online.

But Hubspot is returrning error. No issue of timing, as it’s more than a week already.

I belive, the hubpost code is doing the lookup on main [dayschedule.com](http://dayschedule.com) instead the subdomain `@.dayschedule.com` . While we can’t add TXT record on main domain due to existing TXT record for mailbox etc.

**AWS Screenshot:**

 ![dayschedule_1-1681126561488.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/6/0/6097e5e3e834e190ace080e50b556016d9f8066b.png)

**DNS Screenshot**

[https://dnschecker.org/#TXT/@.dayschedule.com](https://dnschecker.org/#TXT/@.dayschedule.com)

 ![dayschedule_0-1681126546130.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/e/7/e75bce0d4592a6f8aaed4342e054b62f008da8d6.png)

**Hubspot error:**

 ![dayschedule_2-1681126243348.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/c/d/cd19f11b311048ccfe2ce61fd53bb645d5be60fc.png)

 ![dayschedule_0-1681126099236.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/f/f968a5096dc610f5705715a2151f394d9ffc630a.png)

---

<div class="post-metadata">

**Author:** ![MiaSrebrnjak](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/miasrebrnjak/32/10_2.png) [@MiaSrebrnjak](https://community.hubspot.com/u/MiaSrebrnjak)\
**Post date:** [April 11, 2023, 11:35am UTC](https://community.hubspot.com/t/verify-domain-doesnt-work-properly/78977/2 "2023-04-11T11:35:08Z")

</div>

Hi @dayschedule,

Thank you for reaching out to the Community!

I’ll have a deeper look at this with our product expert team – could you send me your account data in a direct message via my Community profile (account ID, your email address)? Thank you!

Cheers  
Mia, Community Team

---

<div class="post-metadata">

**Author:** ![dayschedule](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@dayschedule](https://community.hubspot.com/u/dayschedule)\
**Post date:** [April 11, 2023, 11:42am UTC](https://community.hubspot.com/t/verify-domain-doesnt-work-properly/78977/3 "2023-04-11T11:42:20Z")

</div>

Hi @MiaSrebrnjak

We were able to set the TXT record on primary domain to get it working. So, for me it’s resolved.

But you may check it with your team to confirm if they really want to verify in `@.domain.com` or `domain.com` to update your documentation.

Because, on your website popup it says **HOST NAME: @**

---

<div class="post-metadata">

**Author:** ![MiaSrebrnjak](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/miasrebrnjak/32/10_2.png) [@MiaSrebrnjak](https://community.hubspot.com/u/MiaSrebrnjak)\
**Post date:** [April 12, 2023, 1:59pm UTC](https://community.hubspot.com/t/verify-domain-doesnt-work-properly/78977/4 "2023-04-12T13:59:21Z")

</div>

I’m glad that you were able to resolve the issue! 👍

Thanks for flagging, I’ll send this to our product team for review.

Cheers  
Mia, Community Team