Hubspot DNS records not propagating because of the underscore 'hs1-20286875._domainkey.mydomain.com'

Website, Application, Performance DNS & Network
1

Hello everyone,
I am configuring hubspot cname records. But it seems that my records are not propagating due to the underscore.

I have an article that says that I need to contact support. But that just doesn’t sound right.

I am just trying to verify & find a solution.

Thank you,
W

3

Those underscores are perfectly ok. But if you’ve :orange: Proxied those records, they won’t work.

4 Likes
4

I do not have the cname records proxied & they have been present in cloudflare for more than a day.

Advice is welcome because I am puzzled.
Will

5

We could probably help you better if you shared your domain and tell us what records exactly you have added.

3 Likes
6

I am creating cname records in couldflare:
name:
'hs1-20286875._domainkey'
target:
'seamgroup-com.hs07a.dkim.hubspotemail.net'

I am also having issues with:
Name:
'Managevp-staging.seamgroup.com'
Target:
'managevp-stg.azurewebsites.net'

Just seems like they are not propagating…
Thank you,
Will

7

Can you share a screenshot of https://dash.cloudflare.com/?to=/:account/:zone/dns/records (select your domain) that shows your records AND the assigned Cloudflare nameservers below?

Could you also check if at https://dash.cloudflare.com/?to=/:account/:zone/dns/settings (select your domain), CNAME flattening is set to apex only?

1 Like
8

The second exists as an A record. The first doesn’t exist. Are you sure you’re in the active zone for this domain in Cloudflare?

dig Managevp-staging.seamgroup.com

; <<>> DiG 9.10.6 <<>> Managevp-staging.seamgroup.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61004
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;Managevp-staging.seamgroup.com.	IN	A

;; ANSWER SECTION:
Managevp-staging.seamgroup.com.	30 IN	A	20.119.128.10

;; Query time: 188 msec
;; SERVER: 172.64.36.1#53(172.64.36.1)
;; WHEN: Fri Oct 20 15:40:44 EDT 2023
;; MSG SIZE  rcvd: 75
9

Also ensure you don’t have flatten all cnames enabled if you’re on a paid plan…

1 Like
10

cscharff,
You were right. Cname flattening was causing my error. Thank you for the help!
Will

2 Likes
11

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.