topic Re: Problem with DNS records in Knowledge Base Tool

Problem with DNS records

RumpleAndStilt — Sun, 05 Apr 2026 17:59:41 GMT

Hi, I am attempting to publish a landing page for my brand at the address https://rumpleandstiltskin.com. I connected the domain, but when the DNS records were verifying, it showed an error stating that some records hadn't been connected. (I do not have a screenshot of this error screen.) I checked with my domain provider, Spaceship, and they said that all records are inputed; so I decided to continue. I verified SSL certificate, etc., and published the website, but it now appears under the URL https://rumpleandstiltskin.com/rumple-and-stilts-kin, and I want to be able to direct people to rumpleandstiltskin.com easily and without the content slug. So I removed the content slug to make the site a homepage, but now I receive a 404 error when I go to the site. When I double-checked, the A records and CNAME show up just fine. But when I go to my domain and "set as ready for publishing", this message appears:

What error might be going on with these DNS records? I'd like to know the exact records to update so that the site can be visible as a homepage, but HubSpot's AI isn't helping. Any ideas? Thanks in advance and God bless

Re: Problem with DNS records

emma- — Mon, 06 Apr 2026 08:32:33 GMT

This usually comes down to a root domain / DNS setup issue in HubSpot.

The “Ready for publishing” toggle itself doesn’t fix a 404 — it only affects whether content can be published, not domain resolution.

To fix the 404, you can double-check:

Your primary domain is correctly set in HubSpot settings
DNS records (A record / CNAME) are pointing to HubSpot correctly
DNS propagation has fully completed (can take some time)

Once the domain is correctly connected and verified, the 404 should resolve.

Re: Problem with DNS records

RumpleAndStilt — Mon, 06 Apr 2026 18:12:21 GMT

Thanks for your reply, Emma. I have double-checked the domain and all records, and it has been almost 48 hours since connecting the domain, so the DNS records should have had time to propogate, yet the issue is still not resolved. Should I try disconnecting and reconnecting the domain? I have done this multiple times before with the same results as above, but do you think a screenshot and detailed description of what's happening during setup would help us be able to find a solution?

Re: Problem with DNS records

STierney — Mon, 06 Apr 2026 18:20:05 GMT

Hey @RumpleAndStilt,

Thanks for posting in the Community!

I realize this must be frustrating after several attempts and giving the system time to update, so I'd like to tag in a couple of domain experts who might be able to shed some light on how to troubleshoot this while we await further updates from @emma-.

@Humashankar and @Markestac - any insight here?

Shane, Senior Community Moderator

Re: Problem with DNS records

RumpleAndStilt — Mon, 06 Apr 2026 18:36:52 GMT

Thanks so much for the help, STierney.

Re: Problem with DNS records

MGrace6 — Tue, 07 Apr 2026 06:06:08 GMT

This feels less like a propagation issue and more like a root vs subdomain

misconfiguration in HubSpot. If your page worked with a slug but 404s at the root, it usually means the root domain isn’t properly mapped to a primary page or HubSpot isn’t resolving it as the default. I wouldn’t keep reconnecting—rather confirm the exact A record IP + whether you’re using root (@) vs www and which one is set as primary in HubSpot.

Happy to help you fix this directly, can you confirm if you’re pointing the root domain (@) via A record or redirecting it to www via CNAME?

Re: Problem with DNS records

STierney — Tue, 07 Apr 2026 17:09:53 GMT

Hey @RumpleAndStilt,

Just making sure you see @MGrace6 's message!

Shane, Senior Community Moderator

Re: Problem with DNS records

RumpleAndStilt — Tue, 07 Apr 2026 20:20:31 GMT

Hey MGrace, thanks for your reply. I am redirecting the root domain to www via CNAME. Should this be changed?

Re: Problem with DNS records

STierney — Tue, 07 Apr 2026 20:31:57 GMT

Hey @RumpleAndStilt,

Thanks for this information! Re-tagging @MGrace6.

Shane, Senior Community Moderator

Re: Problem with DNS records

RumpleAndStilt — Thu, 09 Apr 2026 15:58:54 GMT

@MGrace6 @STierney @emma- @Humashankar does anyone have any more ideas as to how to get this resolved? I'd like to have my home domain up as soon as possible, or I might switch to a different provider.

Re: Problem with DNS records

STierney — Thu, 09 Apr 2026 17:06:46 GMT

Hey @RumpleAndStilt,

Tagging in a few more people for visibility, as I realize this is time-sensitive. @Teun, @Indra, and @jonchim - any insight on this setup?

Shane, Senior Community Moderator

Re: Problem with DNS records

Humashankar — Thu, 09 Apr 2026 18:49:02 GMT

Hi @RumpleAndStilt

This seems like a domain-mapping problem, not a page-title problem, root domains need A records, while subdomains like www use CNAME records. If HubSpot shows a DNS verification error, it usually means one of three things. a typo, a missing record, or a conflicting record on the DNS host.

The most likely mismatch is that the root domain rumpleandstiltskin.com is not pointed exactly the way HubSpot expects, even if Spaceship shows records “present.” HubSpot’s domain connection flow says to copy the exact Host and Required Data values from HubSpot into your DNS provider, then verify again. If you published the page under a slug first and then removed the slug, the homepage can go 404 if the domain is connected but the page is not actually assigned to the root URL

Check on these,

Confirm the root domain has the exact HubSpot A record for @ or the apex host, not a CNAME.

Confirm www has the exact HubSpot CNAME target, if you want www.rumpleandstiltskin.com to work too.

Remove conflicting records for the same hostname, especially old A, CNAME, or AAAA records that can block verification.

Recheck the DNS table in HubSpot and compare each row against Spaceship character-for-character.

Regards

Re: Problem with DNS records

RumpleAndStilt — Thu, 09 Apr 2026 20:52:14 GMT

Thanks so much for your response @Humashankar. I have verified the A records for the root domain, the CNAME target for the redirection, checked to make sure old records have been removed, and confirmed each record. There are no errors on either end. What else could I try?