I worked with a network engineer, helpdesk, and my certified HubSpot implementation partner to get a couple subdomains configured. One of them (info.xxx for landing pages) is set up and functional. The other (email.xxx for web versions of emails) simply is not working. We set them up the same way and it seems the CNAME is not propagating for the email.xxx subdomain. HubSpot support said they can't help any further because this is a reverse proxy setup, and my neteng said everything is copied over into our DNS correctly (and, again, another subdomain we configured on the same day worked perfectly within minutes of the config).
What do I do next? Delete the email.xxx subdomain and run through the steps again, or is there some more sophisticated type of troubleshooting I can do first?
Could you try using https://mxtoolbox.com/ to check if the CNAME for email subdomain has propagated worldwide?
Glad I could help. Solving HubSpot puzzles is what we do. Ernesto // GiantFocal Found this answer helpful? Marking it as the solution helps both the community and me - thanks in advance!
Hey y there @Ceej and welcome to the Community. Looks like you've got some good advice so far - I'd have said the same thing @GiantFocal said about the time. But two weeks is a long time.
Have you used DNS checkers and reviewed all proxy HubSpot settings? If your engineer has, then if it were me, I'd delete and try again.
FWIW, I did find these ideas in some light research, also.
Flush DNS: Clear local resolver and browser cache, as well as flush public DNS relays (rarely necessary, but can eliminate local propagation issues).
Verify with a Test Record (I epsecially like this one): Temporarily point email.xxx to a simple CNAME like “example.com” and check propagation independently of HubSpot. If even that doesn’t resolve, the problem is definitely at the DNS/provider level.
Check with Your Registrar: If propagation issues persist longer than 24–48 hours and a working config doesn’t resolve the issue, open a ticket with your DNS provider.
Hopefully that helps!
Did my answer help? Please "mark as a solution" to help others find answers. Plus I really appreciate it!
I use all tools available to help answer questions. This may include other Community posts, search engines, and generative AI search tools. But I always use my experience and my own brain to make it human.
Hey y there @Ceej and welcome to the Community. Looks like you've got some good advice so far - I'd have said the same thing @GiantFocal said about the time. But two weeks is a long time.
Have you used DNS checkers and reviewed all proxy HubSpot settings? If your engineer has, then if it were me, I'd delete and try again.
FWIW, I did find these ideas in some light research, also.
Flush DNS: Clear local resolver and browser cache, as well as flush public DNS relays (rarely necessary, but can eliminate local propagation issues).
Verify with a Test Record (I epsecially like this one): Temporarily point email.xxx to a simple CNAME like “example.com” and check propagation independently of HubSpot. If even that doesn’t resolve, the problem is definitely at the DNS/provider level.
Check with Your Registrar: If propagation issues persist longer than 24–48 hours and a working config doesn’t resolve the issue, open a ticket with your DNS provider.
Hopefully that helps!
Did my answer help? Please "mark as a solution" to help others find answers. Plus I really appreciate it!
I use all tools available to help answer questions. This may include other Community posts, search engines, and generative AI search tools. But I always use my experience and my own brain to make it human.
Thanks, Dan! Delete and try again was my next step, but I like some of these interim testing steps. I'll coordinate with my engineer and work through all this and then I'll circle back to update the thread here... I know you're all on the edges of your seats! /s
@Ceej😂 maybe not the edge of our seats, but it's always helpful to update threads with solutions for sure! 😊
And as always, happy to help!
Did my answer help? Please "mark as a solution" to help others find answers. Plus I really appreciate it!
I use all tools available to help answer questions. This may include other Community posts, search engines, and generative AI search tools. But I always use my experience and my own brain to make it human.
Briefly considered those steps in the bullets, but my neteng and I decided to just delete and start over, and it was all done in about 4 minutes.
Here's what I think happened. When we initiated the process for email.xxx, we probably unchecked the HubSpot CDN option, forcing it down a reverse proxy rabbit hole. We probably left that option on for info.xxx so we never hit the same wall.
Glad to hear you solved it, and so quickly, @Ceej!
Did my answer help? Please "mark as a solution" to help others find answers. Plus I really appreciate it!
I use all tools available to help answer questions. This may include other Community posts, search engines, and generative AI search tools. But I always use my experience and my own brain to make it human.
Hi @Ceej Thank you for reaching out to the Community! I'd like to invite some community members who are subject matter experts to join this conversation. @Mike_Eastwood@Gaurav_Aggarwal@danmoyle - Would you be able to share any insights on this? Your expertise would be greatly appreciated. Best, Victor
Loop Marketing is a new four-stage approach that combines AI efficiency and human authenticity to drive growth. Learn More
Could you try using https://mxtoolbox.com/ to check if the CNAME for email subdomain has propagated worldwide?
Glad I could help. Solving HubSpot puzzles is what we do. Ernesto // GiantFocal Found this answer helpful? Marking it as the solution helps both the community and me - thanks in advance!
Thanks for your reply! A HubSpot rep shared a similar tool with me on chat yesterday. The CNAME for the email.xxx subdomain is not what I would expect it to be based on what I see for the info.xxx subdomain.
info.xxx - CNAME is pretty short and includes "hubspot"
email.xxx - CNAME is longer, looks less like text, includes "aws" but not "hubspot"
My neteng re-confirmed yesterday that everything was copied into our DNS as provided in the HubSpot UI, so I'm still just at a loss.
How long has it been since the email.xxx subdomain's CNAME was updated?
Even though it doesn't happen often, DNS propagation can take 48 to 72 hours.
Glad I could help. Solving HubSpot puzzles is what we do. Ernesto // GiantFocal Found this answer helpful? Marking it as the solution helps both the community and me - thanks in advance!