topic Re: Double A-records do confuse United Domains in Blog, Website & Page Publishing

Double A-records do confuse United Domains

AlexanderHafner — Mon, 30 Jun 2025 11:13:30 GMT

My domian provider (United Domains) is confused by the double A-record entries that Hubspot did ask for. They told me the the site will most likely not publish (and it does not publish) because of the two different IP addresses. Has anyone an idea what is correct and what not. Thanks a lot

Re: Double A-records do confuse United Domains

GiantFocal — Mon, 30 Jun 2025 15:04:34 GMT

Hi @AlexanderHafner,

HubSpot requires two A-records for an important reason: redundancy. If one server has an issue, your website will remain online because the second A-record will point to a working server. This is a standard practice to ensure your website has the best possible uptime and reliability.

So, the information from HubSpot is correct. I would recommend reaching out to United Domains again and explaining that the two A-records are for redundancy and are a hosting requirement with HubSpot.

If it's still not feasible for United Domains, you can try connecting only the primary A record. It should still work, but it will operate without the redundancy that HubSpot provides. Alternatively, a better option is to connect your domain to Cloudflare first and then update the DNS records there.

Re: Double A-records do confuse United Domains

Aakar — Mon, 30 Jun 2025 18:05:33 GMT

@AlexanderHafner - A website can have two A records. If United Domains does not support your requirement, you can try services like Cloudflare to manage your DNS records.

Re: Double A-records do confuse United Domains

AlexanderHafner — Mon, 30 Jun 2025 18:38:44 GMT

Thanks Aakar for your input. I was able to resolve the problem by removing the * allowing the IP to match the Hubspot requierments

Re: Double A-records do confuse United Domains

AlexanderHafner — Mon, 30 Jun 2025 18:40:55 GMT

Thanks Ernesto for your input. I was able to resolve the problem by removing the * allowing the IP to match the Hubspot requierments. The core problem was the slug de/home in the webpage that was set early and not removed to match the URL