I'm using the free version of Hubspot for the moment. This is my site: https://stinsontraining.com and the domain provider is Strato. The site was being hosted on Strato before I created the new pages in Hubspot. Then we hooked the site up to Hubspot, but it keeps going down. We've come to the place where it seems Hubspot expects to have a round-robin dns setup, but Strato is not going to allow more than one A record. So now every time the dns cache expires, the site disconnects. Does anyone have any workarounds for this - any info would be appreciated.
It's a bit odd that Strato is not allowing more than one A record. In this situation, there are two solutions that come to mind:
Transfer domain to a different registrar that allows more control over DNS records.
Connect your website with the "www" to HubSpot, making it load on "www.stinsontraining.com" - this will require only one CNAME record. Assuming Strato allows you to do forwarding, you could then forward "stinsontraining.com" to "www.stinsontraining.com" from the registrar.
Hope this helps!
✔️ Did this post help answer your query? Help the community by marking it as a solution.
In terms of why Round Robin DNS, I have not seen official documentation, but HubSpot is likely using Round Robin DNS for load balancing to distribute incoming web traffic across multiple servers, with the goal of improving performance and reliability.
It is unlikely that they will stop this requirement as it's supported on many domain registrars - and if some don't, the simple solution is simply to change registrars. We've launched dozens of websites with various registrars over the years and never encoutered an issue because of it.
✔️ Did this post help answer your query? Help the community by marking it as a solution.
It's a bit odd that Strato is not allowing more than one A record. In this situation, there are two solutions that come to mind:
Transfer domain to a different registrar that allows more control over DNS records.
Connect your website with the "www" to HubSpot, making it load on "www.stinsontraining.com" - this will require only one CNAME record. Assuming Strato allows you to do forwarding, you could then forward "stinsontraining.com" to "www.stinsontraining.com" from the registrar.
Hope this helps!
✔️ Did this post help answer your query? Help the community by marking it as a solution.
I'am also using Strato and Strato can't help me. Until now I wouldn't like to change the host, so my question is for the variant B.
Can you describe maybe with some screenshot from hubspot domain configuration site, what I have to do? Where I have to put the www for the CNAME and where the forwarding?
And do I have to create a subdomain then in Strato?
Sorry for my questions, maybe you can give me some more informations.
Sure, I can provide some information on this matter.
Based on your screenshot, it looks like that you have already connected the www sub-domain (as it appears in "weitergeleitete domains"). So you likely won't need to create another sub-domain in Strato (unless you want something differenet from www).
Now you would need to click on "Actions" for the domain in "Landing pages" and then select "Replace primary domain"
This should give you an option to select the "www" sub-domain you have connected.
Then if you want your website "xyz.com" to still work, you would need to make it load on "www.xyz.com". This will require to set up domain forwarding (or domain redirect) in Strato. Here are some support documents to help with that:
hi, I'm just reading your solution from yesterday and I think that is exactly what my tech person was thinking of doing. I have a related question - why is Hubspot even requiring a round-robin dns setup and is it not possible from the Hubspot side to stop that requirement? Just wondering if you or anyone else knows.
In terms of why Round Robin DNS, I have not seen official documentation, but HubSpot is likely using Round Robin DNS for load balancing to distribute incoming web traffic across multiple servers, with the goal of improving performance and reliability.
It is unlikely that they will stop this requirement as it's supported on many domain registrars - and if some don't, the simple solution is simply to change registrars. We've launched dozens of websites with various registrars over the years and never encoutered an issue because of it.
✔️ Did this post help answer your query? Help the community by marking it as a solution.